From: Markus Deuling <deuling@de.ibm.com>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Ulrich Weigand <uweigand@de.ibm.com>
Subject: Patch: Remove STOP_UNKNOWN/BREAKPOINT_HIT from infrun.c
Date: Thu, 22 Feb 2007 14:33:00 -0000 [thread overview]
Message-ID: <45DDA9A4.2010005@de.ibm.com> (raw)
Hi,
> Sorry, I missed this message. I think we can remove both of them.
as discussed this patch removes STOP_UNKNOWN and BREAKPOINT_HIT from infrun.c
Ok to commit?
ChangeLog:
* infrun.c (inferior_stop_reason, print_stop_reason): Remove
BREAKPOINT_HIT and STOP_UNKNOWN.
Regards,
Markus
--
Markus Deuling
GNU Toolchain for Linux on Cell BE
deuling@de.ibm.com
=========================================
diff -urN src/gdb/infrun.c dev/gdb/infrun.c
--- src/gdb/infrun.c 2007-01-10 21:10:23.000000000 +0100
+++ dev/gdb/infrun.c 2007-02-22 15:23:34.000000000 +0100
@@ -904,12 +904,8 @@
to the interface from within handle_inferior_event(). */
enum inferior_stop_reason
{
- /* We don't know why. */
- STOP_UNKNOWN,
/* Step, next, nexti, stepi finished. */
END_STEPPING_RANGE,
- /* Found breakpoint. */
- BREAKPOINT_HIT,
/* Inferior terminated by signal. */
SIGNAL_EXITED,
/* Inferior exited. */
@@ -2986,10 +2982,6 @@
{
switch (stop_reason)
{
- case STOP_UNKNOWN:
- /* We don't deal with these cases from handle_inferior_event()
- yet. */
- break;
case END_STEPPING_RANGE:
/* We are done with a step/next/si/ni command. */
/* For now print nothing. */
@@ -3001,10 +2993,6 @@
(uiout, "reason",
async_reason_lookup (EXEC_ASYNC_END_STEPPING_RANGE));
break;
- case BREAKPOINT_HIT:
- /* We found a breakpoint. */
- /* For now print nothing. */
- break;
case SIGNAL_EXITED:
/* The inferior was terminated by a signal. */
annotate_signalled ();
next reply other threads:[~2007-02-22 14:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 14:33 Markus Deuling [this message]
2007-02-22 14:36 ` Daniel Jacobowitz
2007-02-22 14:51 Markus Deuling
2007-02-22 14:55 ` Daniel Jacobowitz
2007-02-22 15:15 ` Ulrich Weigand
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=45DDA9A4.2010005@de.ibm.com \
--to=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