Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@is.elta.co.il>
To: Joel Brobecker <brobecker@ACT-Europe.FR>
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [RFC] gdb_realpath causes problems with GVD
Date: Wed, 20 Mar 2002 03:12:00 -0000	[thread overview]
Message-ID: <Pine.SUN.3.91.1020320130310.27932A-100000@is> (raw)
In-Reply-To: <20020320101408.C22439@act-europe.fr>


On Wed, 20 Mar 2002, Joel Brobecker wrote:

> I have a sad news: filename
> completion does not work in the case you mentionned, but this issue is
> not related to my change. I tried with an unmodified GDB, and got the
> same behavior.

What version of GDB was that, and what debug info format does your 
compiler use?

> I also tried without a simple example without any
> symbolic link, and it did not work either. It only completes if we enter
> the filename without the directory prefix, with and without my change.

This certainly works for me, at least in GDB 5.1.1 with stabs and DWARF2 
debug info.  It doesn't work with COFF debug info, but that's because 
COFF doesn't record the leading directories, only the basename.

Running "objdump --debugging" on the executable should show whether full 
file names with leading directories are recorded or not.

> Shall I go ahead and implement Andrew's suggestions?

I don't have anything against Andrew's suggestions, but they only change 
minor (although important) clerical details.

I don't call the shots in this matter, but I'd certainly hate to lose the 
file-name completion due to this patch.  My suggestion would be to find 
a version of GDB where completion does work, and then see whether your 
changes have any adverse effect on it, before making the decision 
whether to accept the patch.


  reply	other threads:[~2002-03-20 11:12 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 [this message]
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=Pine.SUN.3.91.1020320130310.27932A-100000@is \
    --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