This is the mail archive of the
mailing list for the GDB project.
Re: Spurious SIGTRAP reported by GDB 6.8 when debugging embedded RTOS application
- From: Daniel Jacobowitz <drow at false dot org>
- To: Antony KING <antony dot king at st dot com>
- Cc: Ulrich Weigand <uweigand at de dot ibm dot com>, gdb at sourceware dot org
- Date: Mon, 18 Aug 2008 08:42:05 -0400
- Subject: Re: Spurious SIGTRAP reported by GDB 6.8 when debugging embedded RTOS application
- References: <200808152315.m7FNFeMU025871@d12av02.megacenter.de.ibm.com> <48A94CE7.email@example.com>
On Mon, Aug 18, 2008 at 11:20:23AM +0100, Antony KING wrote:
> Thanks for the explanation. Unfortunately GDB has no influence over the
> RTOS, it is merely an observer. This means that it cannot change the
> status of threads or decide which thread is to execute; this is solely
> under the control of the RTOS.
If GDB has requested a step for a particular thread, and you're
enabling hardware single step in your stub while another thread is
current, I think this must be a bug in the stub. It should, at the
least, report an error instead of continuing.
That said, GDB hasn't been used in this way in a while, though it used
to support it. I think you'll need to communicate to GDB somehow that
it can not change the executing thread.