This is the mail archive of the gdb-patches@sourceware.org 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)


> From: Tom Tromey <tromey@redhat.com>
> Cc: Pedro Alves <pedro@codesourcery.com>, hal9000ed2k@gmail.com,
>         dje@google.com, gdb-patches@sourceware.org, pmuldoon@redhat.com,
>         brobecker@adacore.com, drow@false.org, jan.kratochvil@redhat.com
> Date: Tue, 06 Dec 2011 13:40:16 -0700
> 
> >>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
> 
> Eli> Then maybe "as-recorded"?  Meaning that this is how the compiler
> Eli> recorded the file name in the debug info?
> 
> Works for me.

Thanks for the feedback.  However, I still would like to know whether
my guess regarding the current default, viz.:

  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 correct.  If this is correct, then we will need an additional
setting of the new option.  Or maybe I misunderstand, and the
consensus here is to _rename_ "full" to "as-recorded" and otherwise
leave the implementation intact?


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