From: Daniel Jacobowitz <drow@mvista.com>
To: Kris Warkentin <kewarken@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: deferred breakpoints
Date: Tue, 25 Feb 2003 20:57:00 -0000 [thread overview]
Message-ID: <20030225205711.GA10096@nevyn.them.org> (raw)
In-Reply-To: <00e001c2dd10$3d4284e0$2a00a8c0@dash>
On Tue, Feb 25, 2003 at 03:55:32PM -0500, Kris Warkentin wrote:
> How difficult do you think deferred breakpoints would be to implement? We
> have a customer who does a lot of work with shared objects and they'd like
> to be able to set breakpoints in them and have them persist across runs.
> I'm thinking that creating a list of breakpoints that could be run through
> every time a shared object was loaded would do the trick. Can anyone point
> out any obvious gotcha's?
I'll do you one better - Apple posted patches for this some time ago,
they can probably dig out an updated version for you if you inquire.
It was called "future break".
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-02-25 20:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-25 20:51 Kris Warkentin
2003-02-25 20:57 ` Daniel Jacobowitz [this message]
2003-02-25 21:36 Kris Warkentin
2003-02-25 21:59 ` Jason Molenda
2003-02-26 2:22 ` Kris Warkentin
2003-02-26 4:47 ` Jason Molenda
2003-02-26 16:51 ` Kris Warkentin
[not found] <1046355813.623.ezmlm@sources.redhat.com>
2003-03-01 2:16 ` Jim Ingham
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=20030225205711.GA10096@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=kewarken@qnx.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