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)
Subject: Re: Patch: Remove STOP_UNKNOWN/BREAKPOINT_HIT from infrun.c
Date: Thu, 22 Feb 2007 15:15:00 -0000 [thread overview]
Message-ID: <200702221514.l1MFEwMS002338@d12av02.megacenter.de.ibm.com> (raw)
In-Reply-To: <20070222145458.GA2036@caradoc.them.org> from "Daniel Jacobowitz" at Feb 22, 2007 09:54:58 AM
Daniel Jakobowitz wrote:
> On Thu, Feb 22, 2007 at 03:51:00PM +0100, Markus Deuling wrote:
> > Ok to commit?
> >
> >
> > ChangeLog:
> >
> > * infrun.c (inferior_stop_reason, print_stop_reason): Remove
> > BREAKPOINT_HIT and STOP_UNKNOWN.
>
> OK, thanks.
I've checked this in, thanks.
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2007-02-22 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 14:51 Markus Deuling
2007-02-22 14:55 ` Daniel Jacobowitz
2007-02-22 15:15 ` Ulrich Weigand [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-22 14:33 Markus Deuling
2007-02-22 14:36 ` Daniel Jacobowitz
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=200702221514.l1MFEwMS002338@d12av02.megacenter.de.ibm.com \
--to=uweigand@de.ibm.com \
--cc=deuling@de.ibm.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
/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