This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: idle thread stack full?
On Tue, Oct 23, 2007 at 06:56:04PM +0200, Michele Paselli wrote:
> Hi,
>
> I have an application with 6 threads running and after a while gdb
> stops and I get this message.
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x0006c7dc in idle_thread_stack ()
>
> The address is in RAM and it belongs to the idle thread, is it
> possible that I'm filling completely the idle thread stack? When I
> increase the stack size the application run without errors for more
> time but since I set the option to have a separate stack for
> interrupts I don't understand who's filling the idle thread stack, am
> I missing something?
It probably is not the idle thread which is causing the problem. Any
stack which is corrupted or overflowed could cause a jump which lands
in the idle stack. Can you get a backtrace from gdb? That might give
you a clue.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss