From: Nick Roberts <nickrob@snap.net.nz>
To: gdb-patches@sources.redhat.com
Subject: [PATCH] PR mi/2086 -break-insert missing error diagnostic
Date: Tue, 17 Oct 2006 21:10:00 -0000 [thread overview]
Message-ID: <17717.17922.450312.898237@kahikatea.snap.net.nz> (raw)
This patch fixes PR mi/2086. There may be similar bugs arising from using
catch_exceptions_with_msg inappropriately.
I could slowly work my way through the mi PRs in the bug database. Can I close
a bug or is that another level? (I don't know my password, if I have one).
--
Nick http://www.inet.net.nz/~nickrob
*** gdb.h 18 Dec 2005 11:33:59 +1300 1.5
--- gdb.h 18 Oct 2006 02:57:25 +1300
***************
*** 53,60 ****
/* Create a breakpoint at ADDRESS (a GDB source and line). */
enum gdb_rc gdb_breakpoint (char *address, char *condition,
int hardwareflag, int tempflag,
! int thread, int ignore_count,
! char **error_message);
/* Switch thread and print notification. */
enum gdb_rc gdb_thread_select (struct ui_out *uiout, char *tidstr,
--- 53,59 ----
/* Create a breakpoint at ADDRESS (a GDB source and line). */
enum gdb_rc gdb_breakpoint (char *address, char *condition,
int hardwareflag, int tempflag,
! int thread, int ignore_count);
/* Switch thread and print notification. */
enum gdb_rc gdb_thread_select (struct ui_out *uiout, char *tidstr,
*** breakpoint.c 09 Aug 2006 09:32:37 +1200 1.229
--- breakpoint.c 18 Oct 2006 03:04:02 +1300
*************** do_captured_breakpoint (struct ui_out *u
*** 5466,5473 ****
enum gdb_rc
gdb_breakpoint (char *address, char *condition,
int hardwareflag, int tempflag,
! int thread, int ignore_count,
! char **error_message)
{
struct captured_breakpoint_args args;
args.address = address;
--- 5466,5472 ----
enum gdb_rc
gdb_breakpoint (char *address, char *condition,
int hardwareflag, int tempflag,
! int thread, int ignore_count)
{
struct captured_breakpoint_args args;
args.address = address;
*************** gdb_breakpoint (char *address, char *con
*** 5476,5483 ****
args.tempflag = tempflag;
args.thread = thread;
args.ignore_count = ignore_count;
! return catch_exceptions_with_msg (uiout, do_captured_breakpoint, &args,
! error_message, RETURN_MASK_ALL);
}
--- 5475,5481 ----
args.tempflag = tempflag;
args.thread = thread;
args.ignore_count = ignore_count;
! return do_captured_breakpoint (uiout, &args);
}
next reply other threads:[~2006-10-17 21:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 21:10 Nick Roberts [this message]
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
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=17717.17922.450312.898237@kahikatea.snap.net.nz \
--to=nickrob@snap.net.nz \
--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