This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: single-step breakpoints
- From: Daniel Jacobowitz <drow at false dot org>
- To: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 1 May 2006 09:54:52 -0400
- Subject: Re: single-step breakpoints
- References: <200604252039.k3PKdaZ5020227@elgar.sibelius.xs4all.nl> <20060425210200.GA1153@nevyn.them.org> <200604252154.k3PLscQe005675@elgar.sibelius.xs4all.nl> <200604292314.k3TNE3uH012648@elgar.sibelius.xs4all.nl>
On Sun, Apr 30, 2006 at 01:14:03AM +0200, Mark Kettenis wrote:
> Yes, erroring out is defenitely a better approach than warn and have
> things run away. Here's a patch and some adjustments to the testsuite
> to prevent the tests from going into an infinite loop.
>
> ok?
>
>
> Index: ChangeLog
> from Mark Kettenis <kettenis@gnu.org>
>
> * breakpoint.c (insert_single_step_breakpoint): Make a failure to
> insert a single-step breakpoint an error instead of a warning.
>
> * breakpoint.c (remove_single_step_breakpoints): Bail out early if
> no breakpoints are inserted.
Yeah, I think this is OK.
Ideally, of course, we wouldn't error here. But I'm not sure what
would be more sensible to do. We could quietly finish instead, but
that would go more than one instruction - quite bad.
--
Daniel Jacobowitz
CodeSourcery