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/15694] New: Extra =breakpoint-modified events at startup when using dprintf
Date: Thu, 27 Jun 2013 19:14:00 -0000	[thread overview]
Message-ID: <bug-15694-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=15694

            Bug ID: 15694
           Summary: Extra =breakpoint-modified events at startup when
                    using dprintf
           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, when I set a dprintf before starting the execution of the
inferior, I see 4 unexpected =breakpoint-modified events for each such dprintf,
when starting the inferior.  These events seem identical and don't seem
necessary.

Session showing the events:

> gdb.7.7 -i mi loopfirst
=thread-group-added,id="i1"
~"GNU gdb (GDB) 7.6.50.20130627-cvs\n"
(gdb) dprintf 8,"h"
&"dprintf 8,\"h\"\n"
~"Dprintf 1 at 0x400570: file loopfirst.cc, line 8.\n"
=breakpoint-created,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
\\"h\\""},original-location="/home/lmckhou/testing/loopfirst.cc:8"}
^done
(gdb) r
&"r\n"
~"Starting program: /home/lmckhou/loopfirst \n"
=thread-group-started,id="i1",pid="6709"
=thread-created,id="1",group-id="i1"
^running
*running,thread-id="all"
(gdb) 
=library-loaded,id="/lib64/ld-linux-x86-64.so.2",target-name="/lib64/ld-linux-x86-64.so.2",host-name="/lib64/ld-linux-x86-64.so.2",symbols-loaded="0",thread-group="i1"
=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={"printf
\\"h\\""},original-location="/home/lmckhou/testing/loopfirst.cc:8"}
=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={"printf
\\"h\\""},original-location="/home/lmckhou/testing/loopfirst.cc:8"}
=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={"printf
\\"h\\""},original-location="/home/lmckhou/testing/loopfirst.cc:8"}
=library-loaded,id="/lib/x86_64-linux-gnu/libc.so.6",target-name="/lib/x86_64-linux-gnu/libc.so.6",host-name="/lib/x86_64-linux-gnu/libc.so.6",symbols-loaded="0",thread-group="i1"
=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={"printf
\\"h\\""},original-location="/home/lmckhou/testing/loopfirst.cc:8"}

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2013-06-27 19:14 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 19:14 marc.khouzam at ericsson dot com [this message]
2013-06-27 20:31 ` [Bug breakpoints/15694] " marc.khouzam at ericsson 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-15694-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).