This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug c++/13225] GDB fails to find non-overloaded C++ function
- From: "keiths at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Tue, 11 Oct 2011 18:53:23 +0000
- Subject: [Bug c++/13225] GDB fails to find non-overloaded C++ function
- Auto-submitted: auto-generated
- References: <bug-13225-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=13225
Keith Seitz <keiths at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |ASSIGNED
CC| |keiths at redhat dot com
AssignedTo|unassigned at sourceware |keiths at redhat dot com
|dot org |
--- Comment #1 from Keith Seitz <keiths at redhat dot com> 2011-10-11 18:53:23 UTC ---
There are actually two problems mentioned here. First, the fact that the parser
is seeing the NULL ("0") char const** parameter as an INT, but the evaluator
will not allow that conversion. I don't see why we couldn't permit that. I can
imagine scenarios where the user might want to pass an address this way. While
a real source file would require the cast, there is no reason why we cannot be
a little more permissive in the debugger.
Second, there is a bug alluded to by the OP: casting the first "0" to some
other type will get gdb to "work." This is happening because when the
function's overload suitability is calculated, the code is currently early
returning on the very first non-STANDARD rank that it sees, instead of
returning the worst one that it sees.
Patch/tests pending.
--
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.