Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bug-gdb@rich-paul.net, bug-gdb@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [RFA] Fix file name generation in edit_command (was: Ver 6.3 edit command failing)
Date: Wed, 27 Apr 2005 14:36:00 -0000	[thread overview]
Message-ID: <20050427143620.GA1686@nevyn.them.org> (raw)
In-Reply-To: <01c54b35$Blat.v2.4$c3f52520@zahav.net.il>

On Wed, Apr 27, 2005 at 05:30:11PM +0300, Eli Zaretskii wrote:
> > Date: Tue, 12 Apr 2005 09:58:25 -0400
> > From: bug-gdb@rich-paul.net
> > 
> > While using gdb 6.3,  I was having a problem with the directory name and the
> > file name being concatenated by the edit command without an intervening slash.
> > My solution was just to add the slash to the sprintf format string
> > in cli/cli-cmds.c, near line 650.  It worked for me.
> 
> Thanks for pointing this out.
> 
> In fact, the code there had quite a few problems besides the one you
> found: it didn't use symtab->fullname, failed miserably for DOS-style
> d:/foo/bar file names, etc.
> 
> Does anyone object to the following patch?
> 
> 2005-04-27  Eli Zaretskii  <eliz@gnu.org>
> 
> 	* cli/cli-cmds.c (edit_command): Use symtab->fullname if
> 	possible.  Use IS_ABSOLUTE_PATH instead of checking for a literal
> 	'/'.  Make sure there's a slash between the directory and the file
> 	name.  Simplify and clarify the code logic.

I can simplify this a whole lot further :-)

You should use symtab_to_fullname.  Then all the fallback logic is
unnecessary; if symtab_to_fullname fails, GDB does not know where the
file is.

-- 
Daniel Jacobowitz
CodeSourcery, LLC


  reply	other threads:[~2005-04-27 14:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1DLM3u-0000IQ-Vj@lists.gnu.org>
2005-04-27 14:32 ` Eli Zaretskii
2005-04-27 14:36   ` Daniel Jacobowitz [this message]
2005-04-27 15:52     ` Eli Zaretskii
2005-04-27 17:43       ` Mark Kettenis
2005-04-28  7:10         ` Eli Zaretskii
2005-04-27 18:04       ` Daniel Jacobowitz
2005-04-28  7:05         ` Eli Zaretskii
2005-04-28 20:39         ` Eli Zaretskii
2005-04-28 20:42           ` Daniel Jacobowitz
2005-04-28 21:04             ` Eli Zaretskii
2005-04-28 21:18               ` Daniel Jacobowitz
2005-04-29  7:07                 ` Eli Zaretskii

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=20050427143620.GA1686@nevyn.them.org \
    --to=drow@false.org \
    --cc=bug-gdb@gnu.org \
    --cc=bug-gdb@rich-paul.net \
    --cc=eliz@gnu.org \
    --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