From: Daniel Jacobowitz <drow@false.org>
To: Nick Roberts <nickrob@snap.net.nz>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH] PR mi/2086 -break-insert missing error diagnostic
Date: Tue, 17 Oct 2006 21:57:00 -0000 [thread overview]
Message-ID: <20061017215754.GA15210@nevyn.them.org> (raw)
In-Reply-To: <17717.20397.279496.222573@kahikatea.snap.net.nz>
On Wed, Oct 18, 2006 at 10:48:29AM +1300, Nick Roberts wrote:
> > > This patch fixes PR mi/2086. There may be similar bugs arising from using
> > > catch_exceptions_with_msg inappropriately.
> >
> > Is this the whole patch? I guess you updated the caller too.
>
> I have other changes but they're all older. I think that's it but I'll
> check more carefully.
Well, it won't compile as-is, so obviously you haven't tested this
patch on its own :-)
> > I think removing catch_exceptions_with_msg isn't enough - if you look
> > at the call site, it's not prepared for an error() to escape there.
> > It would have to use a cleanup for deprecated_set_gdb_event_hooks.
>
> Heres my take:
>
> I think the problem arises from changes Andrew Cagney made on 2005-01-13.
> It worked before then but was probably a bit of a hack. By removing
> catch_exceptions_with_msg the error propagates back to catch_exception
> with the function argument captured_mi_execute_command:
>
> #14 0x0812fdf8 in catch_exception (uiout=0x8823918, func=0x80ca1e7 <captured_mi_execute_command>, func_args=0xbfc229a4, mask=6) at exceptions.c:469
> #15 0x080ca5de in mi_execute_command (cmd=0x8855220 "-break-insert *", from_tty=
>
> (mi_execute_command was also changed on 2005-01-13).
But we've messed up whatever those saved/restored hooks were.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-17 21:57 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 [this message]
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
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=20061017215754.GA15210@nevyn.them.org \
--to=drow@false.org \
--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