Re: [patch] GDB 7.2: new feature for "backtrace" that cuts path to file (remain filename)

Eli Zaretskii
2011-12-06T13:03:51Z

> From: Pedro Alves <pedro@codesourcery.com>
> Date: Tue, 6 Dec 2011 12:49:47 +0000
> Cc: hal9000ed2k@gmail.com,
> tromey@redhat.com,
> dje@google.com,
> gdb-patches@sourceware.org,
> pmuldoon@redhat.com,
> brobecker@adacore.com,
> drow@false.org,
> jan.kratochvil@redhat.com
>
> > if the command was
> >
> > gcc -c ... /foo/bar/baz.c
> >
> > then GDB will show "/foo/bar/baz.c", but if the compilation command
> > was
> >
> > gcc -c ... baz.c
> >
> > then GDB will show "baz.c".
>
> >
> > Is that correct? If so, calling this `full' is misleading, I think,
>
> If that is correct, than the default isn't "full", but
> the proposed "no-compile-directory" ?

No, it's `full', because the compile directory was "/foo/bar".

> Or maybe your compiler didn't emit the comp_dir attribute in the
> debug info.

"My compiler" in this case identifies itself as

gcc (Ubuntu 4.4.3-4ubuntu5) 4.4.3

I'd be surprised if this version omits comp_dir, but if someone tells
me how to check that, I will.

> I don't really know what is the current default, and I'm now
> confused too. :-)

Then I'm in good company ;-)

> > unless we really change GDB to always show a full absolute file name
> > there. If we don't want to change, I suggest to call it `normal' or
> > maybe `default' (with explanation along the above lines).
>
> I don't think normal or default are good names

Then maybe "as-recorded"? Meaning that this is how the compiler
recorded the file name in the debug info?