From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: drow@false.org (Daniel Jacobowitz)
Cc: deuling@de.ibm.com (Markus Deuling),
gdb-patches@sourceware.org (GDB Patches),
mark.kettenis@xs4all.nl (Mark Kettenis)
Subject: Re: [rfc] Remove dead code in breakpoint.c
Date: Mon, 02 Jul 2007 18:34:00 -0000 [thread overview]
Message-ID: <200707021834.l62IYKMp032628@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070701223433.GB337@caradoc.them.org> from "Daniel Jacobowitz" at Jul 01, 2007 06:34:33 PM
Daniel Jacobowitz wrote:
> On Fri, Jun 22, 2007 at 11:28:23AM +0200, Markus Deuling wrote:
> > * breakpoint.c (insert_bp_location): Remove dead code
> > (DISABLE_UNSETTABLE_BREAK).
> > (disable_breakpoints_in_shlibs)
> > (disable_breakpoints_in_unloaded_shlib): Likewise (comment).
> >
> > Is this ok ?
>
> Yes, this is OK. Thanks.
I've checked this in now, thanks.
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
prev parent reply other threads:[~2007-07-02 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-22 9:30 Markus Deuling
2007-07-01 22:35 ` Daniel Jacobowitz
2007-07-02 18:34 ` Ulrich Weigand [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=200707021834.l62IYKMp032628@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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