From: "Michael Snyder" <msnyder@sonic.net>
To: "Daniel Jacobowitz" <drow@false.org>
Cc: <gdb-patches@sourceware.org>, "Mark Kettenis" <mark.kettenis@xs4all.nl>
Subject: Re: [PATCH] symfile.c, find_separate_debug_file
Date: Fri, 03 Aug 2007 14:47:00 -0000 [thread overview]
Message-ID: <001901c7d5dc$714de440$677ba8c0@sonic.net> (raw)
In-Reply-To: <20070803114033.GA16806@caradoc.them.org>
> Adding "/" to strings is fine; it's when looking at passed in strings
> that you have to check directory separators more carefully.
>
> On Fri, Aug 03, 2007 at 12:10:30AM -0700, Michael Snyder wrote:
> > Well I don't know -- they seemed to hurt when I tried it,
> > and getting rid of them certainly seemed to help.
> >
> > If I type /usr/lib//tmp/foo, isn't that equivalent, at least
> > in some contexts, to typing /tmp/foo?
>
> To my knowledge this is true only in Emacs, not in any normal
> operating system's file access routines. GDB does not run on top of
> Emacs...
>
> Maybe you could describe how it seemed to hurt.
Sure. It generates a string such as
"/usr/local/lib/debug//opt/grbx/lib.so",
which is then passed to the libc function 'open', which fails to find the
file.
When I remove the extra slash, open succeeds.
This is glibc 2.5 running under UML in Scratchbox, on Ubuntu.
Gdb is x86-cross-x86, not that that's probably relevant.
next prev parent reply other threads:[~2007-08-03 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-03 1:14 msnyder
2007-08-03 1:30 ` Daniel Jacobowitz
2007-08-03 4:41 ` Michael Snyder
2007-08-03 11:40 ` Daniel Jacobowitz
2007-08-03 14:47 ` Michael Snyder [this message]
2007-08-03 15:00 ` Daniel Jacobowitz
2007-08-03 15:09 ` Michael Snyder
2007-08-03 15:19 ` Daniel Jacobowitz
2007-08-03 15:49 ` Andreas Schwab
2007-08-03 12:31 ` Eli Zaretskii
2007-08-03 14:43 ` Michael Snyder
2007-08-03 14:51 ` Daniel Jacobowitz
2007-08-03 17:12 ` Eli Zaretskii
2007-08-03 17:26 ` Michael Snyder
2007-08-03 5:54 ` Mark Kettenis
2007-08-03 7:15 ` Michael Snyder
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='001901c7d5dc$714de440$677ba8c0@sonic.net' \
--to=msnyder@sonic.net \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=mark.kettenis@xs4all.nl \
/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