From: Lancelot SIX via Gdb-patches <gdb-patches@sourceware.org>
To: Simon Marchi <simon.marchi@efficios.com>,
Tom Tromey <tom@tromey.com>,
Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
Cc: sourcewarebugz@kyber.fi
Subject: Re: [PATCH] gdb: check for empty strings in get_standard_cache_dir/get_standard_config_dir
Date: Thu, 7 Jan 2021 21:43:37 +0000 [thread overview]
Message-ID: <21cd6bb7-f220-37c6-eef8-ede223a761ae@lancelotsix.com> (raw)
In-Reply-To: <69b9d1e9-ec9c-5bdc-4255-4f59440c0b5f@efficios.com>
Hi
> Ok, I can try this as a follow-up patch, check that the path
> is absolute using the IS_ABSOLUTE_PATH macro. Is a tilde path
> considered absolute? Like
>
> ~/my-cache
> ~smarchi/my-cache
I would be tempted to say that it is not (according to
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html
it seems it is not).
> I suppose that it is, since it's just a shortcut for
> /home/smarchi.
This actually is the most usual pattern, but the home directory of
smarchi could be different. The actual answer is in /etc/passwd or
accessed via getent:
$ getent passwd smarchi | awk -F: '{ print $6 }'
>
> Simon
Lancelot.
next prev parent reply other threads:[~2021-01-07 21:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 20:57 Simon Marchi via Gdb-patches
2021-01-07 21:00 ` Tom Tromey
2021-01-07 21:14 ` Simon Marchi via Gdb-patches
2021-01-07 21:43 ` Lancelot SIX via Gdb-patches [this message]
2021-01-07 21:53 ` Simon Marchi via Gdb-patches
2021-01-07 22:04 ` Lancelot SIX via Gdb-patches
2021-01-07 22:10 ` Simon Marchi via Gdb-patches
2021-01-07 23:39 ` Sergio Durigan Junior via Gdb-patches
2021-01-08 9:45 ` Andrew Burgess
2021-01-08 11:05 ` Christian Biesinger via Gdb-patches
2021-01-08 9:48 ` Andrew Burgess
2021-01-08 15:50 ` [PATCH v2] gdb: check for empty strings in, get_standard_cache_dir/get_standard_config_dir Simon Marchi via Gdb-patches
2021-01-08 17:13 ` Andrew Burgess
2021-01-08 18:47 ` Simon Marchi via Gdb-patches
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=21cd6bb7-f220-37c6-eef8-ede223a761ae@lancelotsix.com \
--to=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=simon.marchi@efficios.com \
--cc=sourcewarebugz@kyber.fi \
--cc=tom@tromey.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