public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "marc.khouzam at ericsson dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/15693] New: Extra *running event when call-style dprintf hits
Date: Thu, 27 Jun 2013 19:05:00 -0000 [thread overview]
Message-ID: <bug-15693-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=15693
Bug ID: 15693
Summary: Extra *running event when call-style dprintf hits
Product: gdb
Version: HEAD
Status: NEW
Severity: normal
Priority: P2
Component: breakpoints
Assignee: unassigned at sourceware dot org
Reporter: marc.khouzam at ericsson dot com
With HEAD of June 27 which has the fix to Bug 15075, I'm seeing an un-expected
*running event each time a dprintf is hit in the dprintf-style 'call'.
Here is an cleaned up session showing the problem:
> gdb.7.7 -i mi loopfirst
=thread-group-added,id="i1"
~"GNU gdb (GDB) 7.6.50.20130627-cvs\n"
(gdb) -dprintf-insert 8 "hello\n"
^done,bkpt={number="1",type="dprintf",disp="keep",enabled="y",addr="0x0000000000400570",func="main()",file="loopfirst.cc",fullname="/home/lmckhou/testing/loopfirst.cc",line="8",thread-groups=["i1"],times="0",script={"printf
\"hello\\n\""},original-location="/home/lmckhou/testing/loopfirst.cc:8"}
(gdb) set dprintf-style call
&"set dprintf-style call\n"
=breakpoint-modified,bkpt={number="1",type="dprintf",disp="keep",enabled="y",addr="0x0000000000400570",func="main()",file="loopfirst.cc",fullname="/home/lmckhou/testing/loopfirst.cc",line="8",thread-groups=["i1"],times="0",script={"call
(void) printf
(\\"hello\\\\n\\")"},original-location="/home/lmckhou/testing/loopfirst.cc:8"}
=cmd-param-changed,param="dprintf-style",value="call"
^done
(gdb) -exec-run
=thread-group-started,id="i1",pid="6627"
=thread-created,id="1",group-id="i1"
^running
*running,thread-id="all"
(gdb)
[...]
=breakpoint-modified,bkpt={number="1",type="dprintf",disp="keep",enabled="y",addr="0x0000000000400570",func="main()",file="loopfirst.cc",fullname="/home/lmckhou/testing/loopfirst.cc",line="8",thread-groups=["i1"],times="1",script={"call
(void) printf
(\\"hello\\\\n\\")"},original-location="/home/lmckhou/testing/loopfirst.cc:8"}
hello
*running,thread-id="1"
=> we can see this extra *running event, which is not seen when using the 'gdb'
dprintf-style.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2013-06-27 19:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 19:05 marc.khouzam at ericsson dot com [this message]
2013-06-28 11:05 ` [Bug breakpoints/15693] " palves at redhat dot com
2013-06-28 13:39 ` 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@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: 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).