Date:	Tue, 06 Feb 2001 21:54:44 +0200
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	"Michael N. Filippov" <michael AT idisys DOT iae DOT nsk DOT su>
Message-Id:	<2427-Tue06Feb2001215444+0200-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC:	djgpp AT delorie DOT com
In-reply-to:	<95okn9$rgo$1@news.itfs.nsk.su> (michael@idisys.iae.nsk.su)
Subject:	Re: GCC and long file names
References:	<95okn9$rgo$1 AT news DOT itfs DOT nsk DOT su>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Michael N. Filippov" <michael AT idisys DOT iae DOT nsk DOT su>
> Newsgroups: comp.os.msdos.djgpp
> Date: 6 Feb 2001 10:47:05 GMT
> 
> And if look into .o after compilation with debug information we can see
> "long_long_long" (cut to 14 symbols). this is why it cannot be traced
> in RHIDE for example: it just gives me
> +-[_]----------- Error ----------------+
> ¦                                      ¦
> ¦  Could not find the source file      ¦
> ¦  long_long_long.                     ¦
> ¦                                      ¦
> ¦                                      ¦
> ¦                  OK   _              ¦
> ¦                ________              ¦
> +--------------------------------------+
> 
> test$ gcc --version
> 2.952
> 
> But if i use GCC 2.952 on my Linux
> idisys:~$ gcc --version
> 2.95.2
> 
> It stores entire file name in .o file.
> 
> What can I do ?

Compile with -gstabs+ instead of -g.  What you see is a limitation of
the COFF debug info; switching to stabs lifts that limitation.

GNU/Linux systems use ELF or DWARF for debug info, which is free from
COFF's limitations.

- Raw text -