Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Antony KING <antony.king@st.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>, gdb@sourceware.org
Subject: Re: Spurious SIGTRAP reported by GDB 6.8 when debugging embedded 	RTOS  application
Date: Mon, 18 Aug 2008 18:30:00 -0000	[thread overview]
Message-ID: <20080818124205.GA6958@caradoc.them.org> (raw)
In-Reply-To: <48A94CE7.8010400@st.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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2008-08-18 12:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 15:12 Antony KING
2008-08-16 15:33 ` Ulrich Weigand
2008-08-18 18:16   ` Antony KING
2008-08-18 18:30     ` Daniel Jacobowitz [this message]
2008-08-18 18:36       ` Pedro Alves
2008-08-20  1:31         ` Antony KING
2008-08-18 18:47       ` Antony KING
2008-08-19  0:33         ` Ulrich Weigand
2008-08-20 14:30           ` Antony KING
2008-08-20 14:37             ` Pedro Alves
2008-08-21  3:24               ` Antony KING
2008-08-22 14:58                 ` Ulrich Weigand
2008-08-27 21:38                   ` Antony KING

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080818124205.GA6958@caradoc.them.org \
    --to=drow@false.org \
    --cc=antony.king@st.com \
    --cc=gdb@sourceware.org \
    --cc=uweigand@de.ibm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox