public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andre.poenitz at nokia dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug mi/12554] New: Make -break-list output as useful as 'break info' output
Date: Tue, 08 Mar 2011 12:14:00 -0000	[thread overview]
Message-ID: <bug-12554-4717@http.sourceware.org/bugzilla/> (raw)

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

           Summary: Make -break-list output as useful as 'break info'
                    output
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: minor
          Priority: P2
         Component: mi
        AssignedTo: unassigned@sourceware.org
        ReportedBy: andre.poenitz@nokia.com


Currently -break-list output contains less information then 'break info' output
in cases <MULTIPLE>. Even if all 'sub-breakpoint' share the same information
like function name or file:line, this is not reported. It would be more
convenient from a frontend point of view if at least the shared common
information would be reported. Getting the <MULTIPLE> resolved into several
addresses or "sub-breakpoints" would be even better.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-03-08 12:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-08 12:14 andre.poenitz at nokia dot com [this message]
2013-01-15 17:02 ` [Bug mi/12554] " tromey at redhat dot com
2014-09-12 22:59 ` sergiodj 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-12554-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).