This is the mail archive of the gdb-prs@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]

[Bug gdb/15415] gdb resolves symbolic links when passing argv[0]


http://sourceware.org/bugzilla/show_bug.cgi?id=15415

--- Comment #5 from dje at google dot com ---
Another thing to consider is auxiliary file names based on the name of the
binary.  e.g. ${foo}-gdb.py, ${foo}.dwp.

I can imagine some situations wanting gdb to xfullpath $foo and I can imagine
some situations wanting gdb to realpath $foo.
gdb needs to either try both (maybe fullpath first, then realpath) or give the
user a way to specify which one.
[It would be simplest to do the former if that works in a sufficient number of
cases.]

Given that a realpath operation cannot be undone (one can't get back the
original path), I suggest for now we go back to using xfullpath, and then start
working on support for realpath.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


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