Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com, Ulrich.Weigand@de.ibm.com
Subject: Re: [PATCH] PR mi/2086 -break-insert missing error diagnostic
Date: Fri, 17 Nov 2006 21:16:00 -0000	[thread overview]
Message-ID: <20061117211556.GA13961@nevyn.them.org> (raw)
In-Reply-To: <17718.19901.569519.210795@kahikatea.snap.net.nz>

On Thu, Oct 19, 2006 at 04:52:29AM +1300, Nick Roberts wrote:
> 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.

This is just nasty.  I believe I pointed you at Ulrich's analysis of
this problem upthread:

  http://sources.redhat.com/ml/gdb/2006-10/msg00021.html

It seems pretty clear to me that the patch which switched things to
return the result of catch_exceptions_with_msg was wrong.  The
functions are defined to return an enum gdb_rc.  Can't we make
them do that again?  Simple, obviously correct.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2006-11-17 21:16 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
2006-11-17 21:16             ` Daniel Jacobowitz [this message]
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=20061117211556.GA13961@nevyn.them.org \
    --to=drow@false.org \
    --cc=Ulrich.Weigand@de.ibm.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nickrob@snap.net.nz \
    /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