X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From:	pavenis AT lanet DOT lv
To:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>, djgpp-workers AT delorie DOT com
Date:	Sat, 2 Feb 2002 16:16:25 +0200
MIME-Version:	1.0
Subject:	Re: gcc-3.X and GDB
Message-ID:	<3C5C10D9.12475.218886@localhost>
In-reply-to:	<2593-Fri01Feb2002215456+0200-eliz@is.elta.co.il>
References:	<3C5AF9B4 DOT 14429 DOT 27FDF9 AT localhost> (pavenis AT lanet DOT lv)
X-mailer:	Pegasus Mail for Windows (v4.01)
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On 1 Feb 2002 at 21:54, Eli Zaretskii wrote:

> > From: pavenis AT lanet DOT lv
> > Date: Fri, 1 Feb 2002 20:25:24 +0200
> > 
> > One of troubles with debugging C++ code built with gcc-3.0.X using GDB 
> > (or RHIDE) is that GDB show completely wrong file and line for procedures
> > which don't have debug info (like strcpy()).
> 
> Does it matter what debug info (COFF, stabs, DWARF2) was it compiled
> with?
 
First impression is that it happens if stabs or DWARF debugging information
is used in 2 or more files. It's not enough to have only one file with 
DWARF or stabs debugging info. Also it seems that use of COFF debugging info
does not cause problems.

Verified that with my yesterdays build of gcc-3.0.4 20020131 and both
last updated of binutils-2.11.2 and binutils 2002/01/28 CVS version.
(I tested 2 C++ sources, which uses C++ standard library headers,
2 C sources doesn't seem to cause trouble)

Andris

Andris

- Raw text -