From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Lancelot SIX <lsix@lancelotsix.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v4] [PR gdb/27614] gdb-add-index fails on symlinks.
Date: Sun, 9 May 2021 20:14:02 -0400 [thread overview]
Message-ID: <2697b784-fd81-acb3-c4af-f5a65267c06f@polymtl.ca> (raw)
In-Reply-To: <20210329205224.12859-1-lsix@lancelotsix.com>
On 2021-03-29 4:52 p.m., Lancelot SIX via Gdb-patches wrote:
> Since V3:
> - Do net rely on GDB's maintenance commands to resolve
> symlinks, revert to using readlink while maximizing portability.
>
> Since V2:
> - Use GDB to follow symlink instead of readlink. Unlike
> readlink, GDB is guaranteed to be available.
>
> Since V1:
> - Replace '&>/dev/null' with '>/dev/null 2>&1'
>
> --
>
> PR 27614 shows that gdb-add-index fails to generate the index when its
> argument is a symlink.
>
> The following one liner illustrates the reported problem:
>
> $ echo 'int main(){}'|gcc -g -x c -;ln -s a.out symlink;gdb-add-index symlink
> gdb-add-index: No index was created for symlink
> gdb-add-index: [Was there no debuginfo? Was there already an index?]
> $ ls -l
> -rwxr-xr-x 1 25712 Mar 19 23:05 a.out*
> -rw------- 1 8277 Mar 19 23:05 a.out.gdb-index
> lrwxrwxrwx 1 5 Mar 19 23:05 symlink -> a.out*
>
> GDB generates the .gdb-index file with a name that matches the name of
> the actual program (a.out.gdb-index here), not the symlink that
> references it. The remaining of the script is looking for a file named
> after the provided argument (would be 'symlink.gdb-index' in our
> example).
>
> gdb/ChangeLog:
>
> PR gdb/27614
> * contrib/gdb-add-index.sh: Fix when called with a symlink as an
> argument.
>
> gdb/testsuite/ChangeLog:
>
> PR gdb/27614
> * gdb.dwarf2/gdb-add-index-symlink.exp: New test.
This is ok, thanks!
Simon
next prev parent reply other threads:[~2021-05-10 0:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-29 20:52 Lancelot SIX via Gdb-patches
2021-04-17 17:16 ` Lancelot SIX via Gdb-patches
2021-05-09 16:45 ` [PING] " Lancelot SIX via Gdb-patches
2021-05-10 0:14 ` Simon Marchi via Gdb-patches [this message]
2021-05-10 22:24 ` Lancelot SIX 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=2697b784-fd81-acb3-c4af-f5a65267c06f@polymtl.ca \
--to=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.com \
--cc=simon.marchi@polymtl.ca \
/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