Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Markus Deuling <deuling@de.ibm.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
		Ulrich Weigand <uweigand@de.ibm.com>
Subject: Re: Patch: Remove STOP_UNKNOWN/BREAKPOINT_HIT from infrun.c
Date: Thu, 22 Feb 2007 14:55:00 -0000	[thread overview]
Message-ID: <20070222145458.GA2036@caradoc.them.org> (raw)
In-Reply-To: <45DDADD4.6070306@de.ibm.com>

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.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2007-02-22 14:55 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 [this message]
2007-02-22 15:15   ` Ulrich Weigand
  -- 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=20070222145458.GA2036@caradoc.them.org \
    --to=drow@false.org \
    --cc=deuling@de.ibm.com \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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