From: "Michael N. Filippov" Newsgroups: comp.os.msdos.djgpp Subject: Re: GCC and long file names Date: 8 Feb 2001 11:57:08 GMT Lines: 36 Message-ID: <95u1ik$veb$1@news.itfs.nsk.su> References: <95okn9$rgo$1 AT news DOT itfs DOT nsk DOT su> <2427-Tue06Feb2001215444+0200-eliz AT is DOT elta DOT co DOT il> NNTP-Posting-Host: idisys.iae.nsk.su Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 8bit X-Trace: news.itfs.nsk.su 981633428 32203 193.124.169.11 (8 Feb 2001 11:57:08 GMT) X-Complaints-To: usenet AT news DOT itfs DOT nsk DOT su NNTP-Posting-Date: 8 Feb 2001 11:57:08 GMT User-Agent: tin/pre-1.4-19990517 ("Psychonaut") (UNIX) (Linux/2.4.0-test1 (i586)) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli Zaretskii wrote: >> From: "Michael N. Filippov" >> 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. Thanks !