From: Luis Machado <lgustavo@codesourcery.com>
To: Sofia <rodinasophie@gmail.com>, gdb@sourceware.org
Subject: Re: GDB breakpoint implementation for multithreaded programms
Date: Sun, 11 May 2014 03:27:00 -0000 [thread overview]
Message-ID: <536EEE1F.6050003@codesourcery.com> (raw)
In-Reply-To: <loom.20140510T235440-169@post.gmane.org>
On 05/10/2014 06:56 PM, Sofia wrote:
> I'm writing my GDB stub and trying to set breakpoints on different threads.
> When I don't ask GDB about the number of threads, It works fine as a single-
> threaded application and breakpoints are set correctly. But when I enter -
> 'info threads', something strange happens.
>
> Firstly, GDB reads the contents of all threads' registers(it's OK). Then I
> enter 'continue' and see that breakpoints are not set at all threads my
> program has. I don't understand why, but the packet Z0(breakpoint packet) is
> only sent to inactive thread. The documentation says that if the thread id is
> not specified, breakpoints will be set at all threads. What's wrong with this
> or where can I read about such GDB behavior?
>
>
>
Is this a software breakpoint (Z0/z0) or a hardware breakpoint we are
talking about?
A software breakpoint should be valid for all threads if the threads are
executing a shared piece of code. If these breakpoints are not
triggering, we may have a bug somewhere.
For hardware breakpoints, the target code (in this case, the remote
stub) is responsible for replicating the hardware breakpoint settings
(register contents) to all threads upon their creation.
What version of GDB are you using?
prev parent reply other threads:[~2014-05-11 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 22:00 Sofia
2014-05-11 3:27 ` Luis Machado [this message]
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=536EEE1F.6050003@codesourcery.com \
--to=lgustavo@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=rodinasophie@gmail.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