public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "palves at redhat dot com" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/15693] Extra *running event when call-style dprintf hits Date: Fri, 28 Jun 2013 11:05:00 -0000 [thread overview] Message-ID: <bug-15693-4717-X2V3Jymunu@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15693-4717@http.sourceware.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.
next prev parent reply other threads:[~2013-06-28 11:05 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-06-27 19:05 [Bug breakpoints/15693] New: " marc.khouzam at ericsson dot com 2013-06-28 11:05 ` palves at redhat dot com [this message] 2013-06-28 13:39 ` [Bug breakpoints/15693] " marc.khouzam at ericsson dot com 2013-06-28 14:24 ` palves at redhat dot com 2013-07-08 8:23 ` teawater at gmail dot com 2014-05-15 23:59 ` palves at redhat dot com 2014-05-29 12:13 ` palves at redhat dot com
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=bug-15693-4717-X2V3Jymunu@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@sourceware.org \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).