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

Eli Zaretskii
2011-12-05T05:17:37Z

> Date: Mon, 05 Dec 2011 05:52:34 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> 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
> Reply-to: Eli Zaretskii <eliz@gnu.org>
>
> And what about the question I asked regarding the default? AFAIK, the
> current behavior is equivalent to `basename', not to `full'.

I think I know the answer. We show by default whatever the compiler
saw on its command line when it compiled the source file. E.g., 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,
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).