[Bug mi/12554] New: Make -break-list output as useful as 'break info' output

[Bug mi/12554] New: Make -break-list output as useful as 'break info' output

[andre.poenitz at nokia dot com]

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.

[Bug mi/12554] Make -break-list output as useful as 'break info' output

[tromey at redhat dot com]

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

Tom Tromey <tromey at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |WAITING
                 CC|                            |tromey at redhat dot com

--- Comment #1 from Tom Tromey <tromey at redhat dot com> 2013-01-15 17:02:15 UTC ---
Could you be more specific?

I ran gdb on the ovldbreak test case from the test suite
and set a breakpoint on foo::overload1arg.
I get output that seems reasonable (I split it up a bit for readability).

First the main breakpoint:

,body=[bkpt={number="1",type="breakpoint",disp="keep",enabled="y",addr="<MULTIPLE>",times="0",original-location="foo::overload1arg"}

Then sub-breakpoints:

,{number="1.1",enabled="y",addr="0x0000000000400908",func="foo::overload1arg()",file="../../../archer/gdb/testsuite/gdb.cp/ovldbreak.cc",fullname="/home/tromey/Space/SecondArcher/archer/gdb/testsuite/gdb.cp/ovldbreak.cc",line="107"}

,{number="1.2",enabled="y",addr="0x000000000040091d",func="foo::overload1arg(char)",file="../../../archer/gdb/testsuite/gdb.cp/ovldbreak.cc",fullname="/home/tromey/Space/SecondArcher/archer/gdb/testsuite/gdb.cp/ovldbreak.cc",line="110"}


... etc (there are 12 of them...).

How would you want this to be changed?

-- 
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.

[Bug mi/12554] Make -break-list output as useful as 'break info' output

[sergiodj at redhat dot com]

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

Sergio Durigan Junior <sergiodj at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|WAITING                     |RESOLVED
                 CC|                            |sergiodj at redhat dot com
         Resolution|---                         |OBSOLETE

--- Comment #2 from Sergio Durigan Junior <sergiodj at redhat dot com> ---
Closing as OBSOLETE due to inactivity.  Feel free to reopen if still valid.

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