From: Eli Zaretskii <eliz@is.elta.co.il>
To: Tom Tromey <tromey@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: Breakpoints in dynamically loaded objects
Date: Wed, 05 Sep 2001 03:20:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1010905131716.13798E-100000@is> (raw)
In-Reply-To: <874s89ov9s.fsf@cygnus.com>
On 8 May 2000, Tom Tromey wrote:
> And, because of the need to "finish" on that second breakpoint before
> enabling the JNI breakpoint, you can't automate it.
Is that because GDB cannot run the debuggee from breakpoint commands?
If so, I suggested patches to allow that (a long time ago). Michael
Snyder asked for lots of testing before it could be accepted, so it got
buried under the backlog.
Maybe we should revive that again. I still have the patches, although by
now they must have suffered from some bitrot. But it shouldn't be hard
to retrofit them, since the changes were quite simple (in a nutshell, GDB
uses a bunch of static variables to control the debuggee, and running the
inferior from a breakpoint command overwrites some of these variables).
next prev parent reply other threads:[~2001-09-05 3:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200005081343.e48DhHu06845@delius.kettenis.local>
[not found] ` <npzoq1cd1w.fsf@zwingli.cygnus.com>
2001-09-05 0:12 ` Tom Tromey
2001-09-05 3:20 ` Eli Zaretskii [this message]
2001-09-05 3:33 ` Eli Zaretskii
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=Pine.SUN.3.91.1010905131716.13798E-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=tromey@cygnus.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