This is the mail archive of the
gdb@sourceware.cygnus.com
mailing list for the GDB project.
Re: C++ Overload testsuite fixes, need someone to verify
- To: Jimmy Guo <guo at cup dot hp dot com>
- Subject: Re: C++ Overload testsuite fixes, need someone to verify
- From: dan at cgsoftware dot com (Daniel Berlin+list.gdb-patches)
- Date: 23 Mar 2000 22:56:58 -0500
- Cc: "Daniel Berlin+list.gdb-patches" <dan at cgsoftware dot com>, gdb at sourceware dot cygnus dot com, gcc at gcc dot gnu dot org
- References: <Pine.LNX.4.10.10003232042220.12024-100000@hpcll168.cup.hp.com>
- Reply-To: dan at cgsoftware dot com
Jimmy Guo <guo@cup.hp.com> writes:
the "{" is on line 48, the first line of the code ("char arg1") is at
49.
I smell a debugging info issue, where your compiler says it starts at
49, and mine says 48.
I think the real solution is to accept 48 and 49, but say anything
else is wrong.
Or fix gcc, if it's broken.
Something is telling me i remember seeing something about this problem
in gcc recently, something about where it's saying the first line of a
functions starts.
Can any of the GCC guys tell me if i'm making this up in my head (I
believe it was related to where it put the note about the function
start or something like that)?
--Dan
> >Can someone verify, that i am correct in thinking you get unexpected
> >failures in gdb.c++/ovldbreak.exp due to "breakpoint info" failures?
> >I have a patch, i just want to make sure it's not me.
> >It appears the source line the test suite expects main to appear on
> >in that file is 49, and main really appears at 48, so the regex to
> >match doesn't work. I diffed the ovldbreak.cc file, and i get no
> >differences.
>
> I think it should report 49, not 48. Line 49 is the first executable
> statement of main. I'm using the HP WDB source, in case you cannot see
> such behavior with sourceware's (in that case I will spend some time
> digging up the fix to submit as a patch).
>
> - Jimmy Guo