* Multi-process breakpoint behavior
@ 2012-09-19 19:21 Marc Khouzam
0 siblings, 0 replies; only message in thread
From: Marc Khouzam @ 2012-09-19 19:21 UTC (permalink / raw)
To: 'gdb@sourceware.org'
Hi,
I've just noticed that the behavior of multi-process
breakpoints has changed since 7.2. I'm trying to figure
out how to update Eclipse to match and I wanted to get some
guidance on GDB's behavior.
In 7.2 (when we added multi-process to Eclipse),
we needed to set breakpoints for each inferior.
That meant that when the user started a second
inferior, Eclipse had to send a new
-break-insert --thread-group i2 <loc>
for every existing breakpoint.
With 7.3, it seems GDB automatically creates
applicable breakpoints when a new inferior is started.
This means that Eclipse currently creates duplicate
breakpoints in GDB for each new inferior.
I was hoping to confirm that starting with 7.3,
when an inferior is started, all breakpoints
(pending or not) are automatically planted by
GDB and need not be re-created by Eclipse.
Thanks for the help
Marc
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2012-09-19 19:21 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-09-19 19:21 Multi-process breakpoint behavior Marc Khouzam
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).