From: Daniel Jacobowitz <dan@codesourcery.com>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Make mi_cmd_break_insert exception-safe.
Date: Fri, 01 Feb 2008 14:25:00 -0000 [thread overview]
Message-ID: <20080201142439.GA28860@caradoc.them.org> (raw)
In-Reply-To: <200802010953.47178.vladimir@codesourcery.com>
On Fri, Feb 01, 2008 at 09:53:46AM +0300, Vladimir Prus wrote:
> So, why bother trying to make gdb_breakpoint non-throwing? I believe
> any such change will be at least as complex as making mi_cmd_break_insert
> exception-safe? If your concern is about gdb_ prefix, how about renaming
> gdb_exception into 'set_breakpoint'?
That's fine too.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-02-01 14:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-27 17:22 Vladimir Prus
2008-01-27 21:29 ` Nick Roberts
2008-01-28 8:22 ` Vladimir Prus
2008-01-28 14:29 ` Nick Roberts
2008-01-31 22:27 ` Daniel Jacobowitz
2008-02-01 6:54 ` Vladimir Prus
2008-02-01 14:25 ` Daniel Jacobowitz [this message]
2008-02-01 14:50 ` Vladimir Prus
2008-02-01 15:09 ` Daniel Jacobowitz
2008-02-01 15:46 ` Doug Evans
2008-02-01 16:16 ` Vladimir Prus
2008-02-01 15:49 ` Doug Evans
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=20080201142439.GA28860@caradoc.them.org \
--to=dan@codesourcery.com \
--cc=gdb-patches@sources.redhat.com \
--cc=vladimir@codesourcery.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