From: Daniel Jacobowitz <drow@mvista.com>
To: "J. Johnston" <jjohnstn@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [WIP] pending breakpoint support
Date: Fri, 05 Dec 2003 04:57:00 -0000 [thread overview]
Message-ID: <20031205045742.GC13705@nevyn.them.org> (raw)
In-Reply-To: <3FBE95D3.4000300@redhat.com>
On Fri, Nov 21, 2003 at 05:46:43PM -0500, J. Johnston wrote:
> I tried leaving the breakpoint around to allow for "break in all shared
> libs" but that experiment fell flat because it ended up creating the same
> breakpoint multiple times as each shared library gets loaded (e.g. it keeps
> finding printf over and over again in libc). This patch still finds the
> first occurrence in a shared library and then deletes the pending
> breakpoint. Are there plans to identify the shared library for a
> breakpoint in the proposed changes?
No concrete plans, but this definitely can and should be addressed
later. I have a couple of ideas but I want to get something
implemented (eventually) before speculating.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-12-05 4:57 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 1:03 J. Johnston
2003-11-19 6:03 ` Eli Zaretskii
2003-11-19 15:07 ` Daniel Jacobowitz
2003-11-19 23:32 ` J. Johnston
2003-11-19 23:52 ` Andrew Cagney
2003-11-21 22:46 ` J. Johnston
2003-11-25 23:20 ` Thomas Fitzsimmons
2003-11-26 20:02 ` J. Johnston
2003-11-26 20:30 ` Michael Snyder
2003-11-26 21:23 ` Thomas Fitzsimmons
2003-11-26 14:37 ` Andrew Cagney
2003-12-05 4:57 ` Daniel Jacobowitz [this message]
2003-11-19 19:47 ` Tom Tromey
[not found] <1069259237.12557.ezmlm@sources.redhat.com>
2003-11-19 19:38 ` 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=20031205045742.GC13705@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jjohnstn@redhat.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