Werner Lemberg wrote:
> > Hmm, indeed some parts of the debug info appear to have the full
> > file name.
>
> Maybe a bug in gcc/g++? IMHO file names in the debug info should
> always be stored as absolute.
To decide whether it's a bug in g++, in gdb, or in Eclipse, wasn't easy.
I've now reported
Werner Lemberg wrote, quoting Bruno Haible:
>> For example, src/roff/troff/input.cpp could be renamed to
>> troffinput.cpp.
>
> Mhmm, doing this is a pain in the neck... I really would like to
> avoid that. BTW, you are the first person who complains.
I completely agree.
To suggest that path na
Werner Lemberg wrote:
> Hmm, working with plain gdb is just fine.
That could be explained if gdb and Eclipse simply have different heuristics
for looking up source files, given a name without directory specification.
> Are you *really* sure that this is a limitation of the ELF format and
> not a
It's definitely not a limitation of the ELF format.
btw, my old IDE doesn't complain (yes, its the trusted "make" 8-}
Best regards
Amitava
-Original Message-
Sent: Tuesday, January 17, 2006 10:50 AM
To: [EMAIL PROTECTED]
Cc: groff@gnu.org
Subject: Re: [Groff] source
> > Are you *really* sure that this is a limitation of the ELF format
> > and not a bug in the Eclipse IDE? I simply can't believe that...
>
> Hmm, indeed some parts of the debug info appear to have the full
> file name.
Maybe a bug in gcc/g++? IMHO file names in the debug info should
always b
> One thing is not comfortable when working with the groff sources: the
> existence of several source files with the same basename. [...]
>
> The problem that it is causing me is that in the Eclipse 3.1 IDE
> that I'm using, when I start the 'troff' program under the debugger,
> the IDE wants to
Hi,
One thing is not comfortable when working with the groff sources: the
existence of several source files with the same basename.
$ find . -name common.cpp
./src/libs/libbib/common.cpp
./src/preproc/pic/common.cpp
$ find . -name input.cpp
./src/libs/libdriver/input.cpp
./src/roff/troff/input.cp
