Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] PR mi/2086 -break-insert missing error diagnostic
Date: Wed, 18 Oct 2006 15:55:00 -0000	[thread overview]
Message-ID: <17718.19901.569519.210795@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20061018153109.GB10436@nevyn.them.org>

Daniel Jacobowitz writes:
 > On Wed, Oct 18, 2006 at 12:44:20PM +1300, Nick Roberts wrote:
 > > The name deprecated_set_gdb_event_hooks suggests that they're earmarked for
 > > removal.  These hooks only seem to get get in one place so presumably they
 > > could be set up once at initialisation and left with that value.
 > 
 > They're also used by insight.  This is one of the sucky things about
 > having insight directly linked to GDB.

OK, how about just using the hack in mi_cmd_thread_select for
mi_cmd_break_insert for the moment.

-- 
Nick                                           http://www.inet.net.nz/~nickrob


*** mi-cmd-break.c	24 Dec 2005 07:57:46 +1300	1.13
--- mi-cmd-break.c	19 Oct 2006 04:46:35 +1300	
***************
*** 25,30 ****
--- 25,31 ----
  #include "mi-out.h"
  #include "breakpoint.h"
  #include "gdb_string.h"
+ #include "exceptions.h"
  #include "mi-getopt.h"
  #include "gdb-events.h"
  #include "gdb.h"
*************** mi_cmd_break_insert (char *command, char
*** 164,170 ****
      }
    deprecated_set_gdb_event_hooks (old_hooks);
  
!   if (rc == GDB_RC_FAIL)
      return MI_CMD_ERROR;
    else
      return MI_CMD_DONE;
--- 165,175 ----
      }
    deprecated_set_gdb_event_hooks (old_hooks);
  
!   /* RC is enum gdb_rc if it is successful (>=0)
!      enum return_reason if not (<0). */
!   if ((int) rc < 0 && (enum return_reason) rc == RETURN_ERROR)
!     return MI_CMD_ERROR;
!   else if ((int) rc >= 0 && rc == GDB_RC_FAIL)
      return MI_CMD_ERROR;
    else
      return MI_CMD_DONE;


  reply	other threads:[~2006-10-18 15:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 21:10 Nick Roberts
2006-10-17 21:31 ` Daniel Jacobowitz
2006-10-17 21:51   ` Nick Roberts
2006-10-17 21:57     ` Daniel Jacobowitz
2006-10-17 22:10       ` Nick Roberts
2006-10-17 23:47       ` Nick Roberts
2006-10-18 15:31         ` Daniel Jacobowitz
2006-10-18 15:55           ` Nick Roberts [this message]
2006-11-17 21:16             ` Daniel Jacobowitz
2006-11-19  4:39               ` Nick Roberts

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=17718.19901.569519.210795@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=drow@false.org \
    --cc=gdb-patches@sources.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