Re: [RFC] gdb_realpath causes problems with GVD

[Joel Brobecker <brobecker@ACT-Europe.FR>]

> What version of GDB was that, and what debug info format does your 
> compiler use?

It was with GNU gdb 2002-03-19-cvs, and I used stabs. I verified in
the assembly file that the path is stored in the debug information, and
that objdump --debugging gives me the path as well.

> This certainly works for me, at least in GDB 5.1.1 with stabs and DWARF2 
> debug info.  It doesn't work with COFF debug info, but that's because 
> COFF doesn't record the leading directories, only the basename.

I tried it with several combinations of GCC, GDB, and debug format, and
did not get it to work until I changed the compilation command to
provide the fullpath of the file I was compiling:

    gcc -g -o toto <fullpath>/toto.c
    
In this case, completion works, and I verified that my change does not
break completion.

As an aside after all my experiments, it seems that the break command is
only using the information corresponding to the DW_AT_name entry (in
stabs, this is the second N_SO entry)...

Is there anything else that I missed regarding this file-completion
issue?
-- 
Joel