From: Tom Tromey <tromey@redhat.com>
To: Joel Brobecker <brobecker@ACT-Europe.FR>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb_realpath causes problems with GVD
Date: Wed, 20 Mar 2002 14:16:00 -0000 [thread overview]
Message-ID: <87adt2ri93.fsf@creche.redhat.com> (raw)
In-Reply-To: Joel Brobecker's message of "Tue, 19 Mar 2002 17:12:37 +0100"
>>>>> "Joel" == Joel Brobecker <brobecker@ACT-Europe.FR> writes:
Joel> The problem appears when some of the files used to build the
Joel> application are symbolic links and when GDB annotations are
Joel> activated. For us, this happens when GVD, our graphical
Joel> front-end, drives GDB.
Joel> Breakpoint 1, break_me () at toto.c:4
Joel> yy/bonn.a/brobecke/symlinks/toto.C:4:23:beg:0x804846b
Joel> As you see, GDB has translated toto.c into toto.C. This
Joel> translation causes GDB to think that the inferior stopped in a
Joel> file named toto.C (which is not known to GDB, since the compiler
Joel> used only toto.c). As a consequence, when the user tries to put
Joel> breakpoints using the GVD, GVD issues the following break
Joel> command
Joel> (gdb) break toto.C:4
gdb tells GVD that the file is "/bonn.a/brobecke/symlinks/toto.C".
Why does GVD then use just the base name?
Won't this be incorrect if there is more than one file with the same
name? (The very problem my original patch was intended to fix.)
Wouldn't changing GVD to pass the exact same file name back to gdb
give correct results in every case?
Joel> I think I found a way to keep the fix to his problem and then at
Joel> the same time fix our issue: instead of canonicalizing the
Joel> entire filename, I suggest that we only expand the directory
Joel> prefix (ie the part returned by the "dirname" unix command).
I suspect this won't be correct in all cases, but I don't have a ready
counterexample.
Tom
next prev parent reply other threads:[~2002-03-20 22:16 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
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 [this message]
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=87adt2ri93.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@ACT-Europe.FR \
--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