This is the mail archive of the mailing list for the GDB project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

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

On Sunday 04 December 2011 19:55:19, Eli Zaretskii wrote:
> > From: Pedro Alves <>
> > On Sunday 04 December 2011 18:41:16, iam ahal wrote:
> > > > of without-compilation-directory.
> > 
> > At the risk of being bikesheddy, I suggest "no-compilation-directory" instead.
> > 5 whole letters less.  :-)  Somehow it sounds more gdb-idiomatic to me.
> Fine with me, but it still falls short of explaining what exactly is
> removed from the file name.

The working directory of the compilation command that produced the
frame's compilation unit.  E.g., with:

$ pwd
$ gcc a/b.c

If the debug info supports a notion of compilation directory (DW_AT_comp_dir
in dwarf), the full name is /foo/bar/a/b.c and the compilation
directory is /foo/bar.  The no-compilation-directory option
would the show a/b.c .

I'd rather have a positive option, rather than a negative one (no-|without-),
but I'm failing to find a better name.  I thought of "relative",
but that's not entirely accurate -- it can be a full path too.  I can live
with no-compilation-directory.  Just saying I tried and failed.

Pedro Alves

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]