[Bug breakpoints/15693] Extra *running event when call-style dprintf hits

["palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

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.