From: Daniel Jacobowitz <drow@false.org>
To: Vladimir Prus <vladimir@codesourcery.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] Make mi_cmd_break_insert exception-safe.
Date: Thu, 31 Jan 2008 22:27:00 -0000 [thread overview]
Message-ID: <20080131221653.GB6715@caradoc.them.org> (raw)
In-Reply-To: <200801271715.08542.vladimir@codesourcery.com>
On Sun, Jan 27, 2008 at 05:15:07PM +0300, Vladimir Prus wrote:
> The gdb_breakpoint function, as I understand it, was supposed to be part of
> libgdb interface, defined in gdb.h header. However, libgdb is not even close to
> being usable, and when I've asked about using gdb as a library some time ago, the
> response was that it's too hard to do, and it's no longer a goal. Therefore,
> I think it makes no sense to keep gdb_breakpoint non-throwing.
There is a convention that the gdb_* functions don't throw, though.
It's very confusing what does and does not throw in GDB. Before this
patch, did gdb_breakpoint actually throw? If so, would fixing it
by using try/catch inside gdb_breakpoint fix this bug too?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-01-31 22:17 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 [this message]
2008-02-01 6:54 ` Vladimir Prus
2008-02-01 14:25 ` Daniel Jacobowitz
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=20080131221653.GB6715@caradoc.them.org \
--to=drow@false.org \
--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