From: "Eli Zaretskii" <eliz@is.elta.co.il>
To: drow@mvista.com
Cc: brobecker@ACT-Europe.FR, gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb_realpath causes problems with GVD
Date: Tue, 19 Mar 2002 11:18:00 -0000 [thread overview]
Message-ID: <3405-Tue19Mar2002211430+0200-eliz@is.elta.co.il> (raw)
In-Reply-To: <20020319123357.A16236@nevyn.them.org> (message from Daniel Jacobowitz on Tue, 19 Mar 2002 12:33:57 -0500)
> Date: Tue, 19 Mar 2002 12:33:57 -0500
> From: Daniel Jacobowitz <drow@mvista.com>
>
> > Is this a complete solution? That is, will it work in a situation
> > slightly different from your, e.g., when one of the directories in the
> > full file name is also a symlink?
>
> I believe it will. We'll have a canonical name for each directory a
> source file was built out of; if the source file was a link, well, it's
> still the name we were given for the source file. Does that seem right
> to you?
I'm not sure yet. My doubt stems from the fact that directories are
also recorded in the debug info, at least with some formats (stabs,
DWARF2). One place in GDB where we use this is in file-name
completion, for example when you type "break /foo TAB" and want GDB
to complete this to "break /foobar/foo.c" (assuming that there's only
one file foo.c in that directory that was compiled into the program).
Will this break if symlinks are followed in the directory part, but
not in the file-name part?
next prev parent reply other threads:[~2002-03-19 19:18 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-19 8:12 Joel Brobecker
2002-03-19 9:17 ` Eli Zaretskii
2002-03-19 9:34 ` Daniel Jacobowitz
2002-03-19 9:56 ` Joel Brobecker
2002-03-19 11:18 ` Eli Zaretskii [this message]
2002-03-19 12:14 ` Joel Brobecker
2002-03-19 22:04 ` Eli Zaretskii
2002-03-20 1:15 ` Joel Brobecker
2002-03-20 3:12 ` Eli Zaretskii
2002-03-20 4:05 ` Joel Brobecker
2002-03-20 10:25 ` Eli Zaretskii
2002-03-20 8:10 ` Andrew Cagney
2002-03-20 9:41 ` Joel Brobecker
2002-03-19 10:29 ` Andrew Cagney
2002-03-19 14:28 ` Joel Brobecker
2002-03-20 14:16 ` Tom Tromey
2002-03-21 0:11 ` Joel Brobecker
2002-03-21 3:44 ` Joel Brobecker
2002-03-23 21:35 ` Tom Tromey
2002-03-25 1:22 ` Joel Brobecker
2002-03-25 9:23 ` Tom Tromey
2002-03-25 10:01 ` Joel Brobecker
2002-03-27 19:36 ` Andrew Cagney
2002-03-27 19:42 ` Daniel Jacobowitz
2002-03-23 21:13 ` Tom Tromey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3405-Tue19Mar2002211430+0200-eliz@is.elta.co.il \
--to=eliz@is.elta.co.il \
--cc=brobecker@ACT-Europe.FR \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox