This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
c++/1468: breakpoint on "A::bar (int) const"
- From: mec dot gnu at mindspring dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 27 Nov 2003 03:08:15 -0000
- Subject: c++/1468: breakpoint on "A::bar (int) const"
- Reply-to: mec dot gnu at mindspring dot com
>Number: 1468
>Category: c++
>Synopsis: breakpoint on "A::bar (int) const"
>Confidential: no
>Severity: serious
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Nov 27 03:18:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: mec.gnu@mindspring.com
>Release: gdb HEAD 2003-11-26
>Organization:
>Environment:
native i686-pc-linux-gnu
gcc 3.3.2
>Description:
This is the residue of PR gdb/34 after the main problem was fixed.
When gdb takes a breakpoint on a function, it likes to print the function name with arguments:
Breakpoint 3 at A::bar (this=0xNNNNNNNN, arg=117) ...
The "const" modifier has been dropped on the floor.
This will be a bit harder to fix than it looks. As the analysis in PR gdb/34 pointed out, the output has to look good for the annotation interface as well as the command line interface. And now there's an MI interface as well.
The annotation interface doesn't have space to put the "const" after the arguments where it would naturally go. I don't know about the MI interface.
>How-To-Repeat:
Run gdb.cp/method.exp and look at the breakpoints taken on A::foo and A::bar.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: