Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@ACT-Europe.FR>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb_realpath causes problems with GVD
Date: Thu, 21 Mar 2002 00:11:00 -0000	[thread overview]
Message-ID: <20020321091144.A30346@act-europe.fr> (raw)
In-Reply-To: <87adt2ri93.fsf@creche.redhat.com>; from tromey@redhat.com on Wed, Mar 20, 2002 at 03:23:19PM -0700

> gdb tells GVD that the file is "/bonn.a/brobecke/symlinks/toto.C".
> Why does GVD then use just the base name?

That's a very good point, and I'll followup with the GVD developers.

There is something in the break command that I haven't understood,
because:

      (gdb) b toto.C:5
      No source file named toto.C.
      (gdb) b /bonn.a/brobecke/toplevel/symlinks/toto.C:4
      Note: breakpoint 1 also set at pc 0x8048583.
      Breakpoint 2 at 0x8048583: file /bonn.a/brobecke/toplevel_link/symlinks/toto.c, line 4.

This seems odd to me that GDB refuses a breakpoint on toto.C, but accepts
a breakpoint on /bonn.a/.../toto.C? I also noticed an inconsistency in the
filename used in the "Breakpoint 2 at ..." line, should this be also
normalized?

> I suspect this won't be correct in all cases, but I don't have a ready
> counterexample.

It would be useful if you could find such a counter example, because it
would help me for future work in GDB to undertand if there was something
I missed.

Supposing that this problem can be corrected entirely in GVD, should I
withdraw my change request? I would still prefer GDB to display toto.c
rather than toto.C as the basename part, but I don't have a strong
opinion so the advice of all GDB developers would be welcome.

-- 
Joel


  reply	other threads:[~2002-03-21  8:11 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
2002-03-21  0:11   ` Joel Brobecker [this message]
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=20020321091144.A30346@act-europe.fr \
    --to=brobecker@act-europe.fr \
    --cc=gdb-patches@sources.redhat.com \
    --cc=tromey@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