From: Andrew Cagney <ac131313@redhat.com>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch / rfc / 5.3] Attempt N++ for gdb_realpath()
Date: Tue, 12 Nov 2002 09:20:00 -0000 [thread overview]
Message-ID: <3DD13854.4010407@redhat.com> (raw)
In-Reply-To: <3DCFDF46.7000900@redhat.com>
> Hello,
>
> This is trying to fix http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gdb&pr=656
>
> It breaks the host system down into:
>
> - realpath() and constant pathmax
>
> - canonicalize file name
>
> - realpath() and pathconf()
>
> - xstrdup()
>
> realpath() is split into two cases - the easy / common one and the nasty horrible pathconf() one. The latter (which was causing grief on GNU) has been moved to the end.
>
> comments? For 5.3 and mainline.
I've checked this in. Now to see what breaks :-/
Andrew
> 2002-11-09 Andrew Cagney <ac131313@redhat.com>
>
> * utils.c (gdb_realpath): Rewrite. Try realpath() with a constant
> buffer, cannonicalize_file_name(), realpath() with a pathconf()
> defined buffer, xstrdup().
>
next prev parent reply other threads:[~2002-11-12 17:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 8:48 Andrew Cagney
2002-11-12 9:20 ` Andrew Cagney [this message]
2002-11-12 12:28 ` Andrew Cagney
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=3DD13854.4010407@redhat.com \
--to=ac131313@redhat.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