From: Tom Tromey <tromey@redhat.com>
To: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [RFA] Avoid calling stat with empty name in relocate_gdb_directory
Date: Thu, 03 Jan 2013 20:59:00 -0000 [thread overview]
Message-ID: <87r4m20yqb.fsf@fleche.redhat.com> (raw)
In-Reply-To: <26262.2907328934$1355473042@news.gmane.org> (Pierre Muller's message of "Fri, 14 Dec 2012 09:16:50 +0100")
>>>>> "Pierre" == Pierre Muller <pierre.muller@ics-cnrs.unistra.fr> writes:
Pierre> I still think that the approach of testing if *dir == '\0'
Pierre> is safer...
That is ok by me.
Tom
next prev parent reply other threads:[~2013-01-03 20:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <29503.7594777115$1354726985@news.gmane.org>
2012-12-05 18:03 ` Tom Tromey
2012-12-05 23:45 ` Pierre Muller
[not found] ` <434.327257289802$1354751122@news.gmane.org>
2012-12-06 18:33 ` Tom Tromey
2012-12-14 8:17 ` Pierre Muller
[not found] ` <26262.2907328934$1355473042@news.gmane.org>
2013-01-03 20:59 ` Tom Tromey [this message]
2013-01-03 22:19 ` Pierre Muller
2012-12-05 17:02 Pierre Muller
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=87r4m20yqb.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pierre.muller@ics-cnrs.unistra.fr \
/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