This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug breakpoints/15693] Extra *running event when call-style dprintf hits
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Fri, 28 Jun 2013 11:05:48 +0000
- Subject: [Bug breakpoints/15693] Extra *running event when call-style dprintf hits
- Auto-submitted: auto-generated
- References: <bug-15693-4717 at http dot sourceware dot org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=15693
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
Yeah, you'll this for all infcalls, not just dprintf+call. E.g., with
something like:
#include <unistd.h>
#include <stdlib.h>
int
return_false (void)
{
return 0;
}
int
main ()
{
while (1)
usleep (1);
}
$ gdb return-false -i=mi
(gdb)
start
...
(gdb)
b 14 if return_false ()
&"b 14 if return_false ()\n"
~"Breakpoint 2 at 0x4004eb: file return-false.c, line 14.\n"
...
^done
(gdb)
c
&"c\n"
~"Continuing.\n"
^running
*running,thread-id="1"
(gdb)
*running,thread-id="1"
*running,thread-id="1"
*running,thread-id="1"
*running,thread-id="1"
*running,thread-id="1"
*running,thread-id="1"
... repeat forever ...
We should be suppressing that if we never told the user/frontend the thread was
stopped.
--
You are receiving this mail because:
You are on the CC list for the bug.