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/15697] New: Unnecessary =breakpoint-modified event when hitting dprintf
Date: Thu, 27 Jun 2013 20:31:00 -0000	[thread overview]
Message-ID: <bug-15697-4717@http.sourceware.org/bugzilla/> (raw)

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

            Bug ID: 15697
           Summary: Unnecessary =breakpoint-modified event when hitting
                    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

I believe there was an agreement that it was not a good idea to send a
=breakpoint-modified event each time a dprintf was hit.  When a dprintf is in a
loop, these event can become quite inefficient.  Furthermore, these events are
not sent when using 'agent' dprintf-style.

Please see discussion and agreement here:
http://sourceware.org/ml/gdb-patches/2013-03/msg00260.html
http://sourceware.org/ml/gdb-patches/2013-03/msg00380.html

(note that if this change is made, it would nullify Bug 15694)

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


             reply	other threads:[~2013-06-27 20:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-27 20:31 marc.khouzam at ericsson dot com [this message]
2014-01-10 16:24 ` [Bug breakpoints/15697] " marc.khouzam at ericsson dot com
2014-04-06  4:09 ` malaperle at gmail dot com
2014-04-28 20:26 ` marc.khouzam at ericsson dot com
2014-06-03 18:09 ` 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-15697-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).