From: Daniel Jacobowitz <drow@false.org>
To: Roland Puntaier <Roland.Puntaier@br-automation.com>
Cc: gdb@sourceware.org
Subject: Re: GDB 6.6, remote, more threads
Date: Mon, 24 Sep 2007 17:04:00 -0000 [thread overview]
Message-ID: <20070924165054.GA22797@caradoc.them.org> (raw)
In-Reply-To: <OF83DF5973.CD824D25-ONC1257360.0059ADF3-C1257360.005BE817@br-automation.com>
On Mon, Sep 24, 2007 at 06:43:44PM +0200, Roland Puntaier wrote:
> Hello,
>
> The following behavior looks strange to me. Could this be a bug in GDB? Or
> maybe I simply miss something.
>
> I have a program with two threads I set up to test my gdbServer. Each
> thread function has 3 lines of code and every line has a breakpoint.
> I do successive 'c's at the Gdb prompt.
>
> Here Gdb gets 'T0505...08:5b698303;..' corresponding to one breakpoint
> ($Z0,383695b,1#b7).
> So GdbServer tells Gdb that a breakpoint was hit, but Gdb ignores it and
> does a 'vCont;c' again.
Try "set debug infrun 1" to see what's going on. What target is this?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-24 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 16:51 Roland Puntaier
2007-09-24 17:04 ` Daniel Jacobowitz [this message]
2007-09-24 17:11 ` Roland Puntaier
2007-09-24 17:20 ` Daniel Jacobowitz
2007-09-24 20:29 ` Roland Puntaier
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=20070924165054.GA22797@caradoc.them.org \
--to=drow@false.org \
--cc=Roland.Puntaier@br-automation.com \
--cc=gdb@sourceware.org \
/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