This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
c++/1061: weird menu choices when setting constructor breakpoints
- From: carlton at math dot stanford dot edu
- To: gdb-gnats at sources dot redhat dot com
- Date: 15 Feb 2003 00:29:58 -0000
- Subject: c++/1061: weird menu choices when setting constructor breakpoints
- Reply-to: carlton at math dot stanford dot edu
>Number: 1061
>Category: c++
>Synopsis: weird menu choices when setting constructor breakpoints
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Sat Feb 15 00:38:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: carlton@math.stanford.edu
>Release: GNU gdb 2003-02-14-cvs
>Organization:
>Environment:
Red Hat 7.3, GCC 3.1, DWARF-2
>Description:
When I try to set a breakpoint on a constructor, I get
bizarre menu choices in some circumstances: if I compile
the following:
class C {
public:
C() {};
};
int main()
{
}
then the following happens:
jackfruit$ /extra/gdb/mirror/src/gdb/gdb a.out
GNU gdb 2003-02-14-cvs
Copyright 2003 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
(gdb) b C::C
[0] cancel
[1] all
?HERE
?HERE
> 0
canceled
If I actually declare a variable of type c somewhere, the
?HERE's get replaced by something more reasonable.
It's not entirely clear to me _exactly_ what the
conditions are to trigger the bug.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: