From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: "Pierre-Loup A. Griffais" <pgriffais@nvidia.com>
Cc: linux-kernel@vger.kernel.org, a.p.zijlstra@chello.nl,
paulus@samba.org, mingo@redhat.com,
torvalds@linux-foundation.org,
Mike Sartain <mikesart@valvesoftware.com>
Subject: Re: [PATCH] perf symbols: Follow .gnu_debuglink section to find separate symbols
Date: Thu, 21 Jun 2012 14:28:59 -0300 [thread overview]
Message-ID: <20120621172859.GA17747@infradead.org> (raw)
In-Reply-To: <4FE24D31.3070608@nvidia.com>
Em Wed, Jun 20, 2012 at 03:22:41PM -0700, Pierre-Loup A. Griffais escreveu:
> The .gnu_debuglink section is specified to contain the filename of the
> debug info file, as well as a CRC that can be used to validate it.
> This provides more context:
> http://sourceware.org/gdb/onlinedocs/gdb/Separate-Debug-Files.html
>
> +++ b/tools/perf/util/symbol.c
> +static int filename__read_debuglink(const char *filename,
> + char *path, size_t size)
> +{
Isn't there any other function that opens an ELF file, looks for an
specific session to then read its contents?
Couldn't it be reused here?
> + case SYMTAB__DEBUGLINK: {
> + char *last_slash;
> + strncpy(name, dso->long_name, size);
> + last_slash = name + dso->long_name_len;
> + while (last_slash && *last_slash != '/')
> + last_slash--;
Why the test for last_slash to be != NULL? How could it ever be? This is
an optimization since we have the dso->long_name_len so that we avoid
using strrchr that in turn would do an strlen?
So the test should be:
while (last_slash != name && *last_slash != '/')
To avoid underflowing, right?
> + if (last_slash)
> + last_slash++;
> + filename__read_debuglink(dso->long_name, last_slash,
How last_slash can point to the path? It looks like it points to the
basename, no?
Yeah, it is, and then your algorithm will work because last_slash
doesn't point to the _path_, but to a string _preceded_ by the path, so
for /bin/ls, the debuglink content would be ls.debug and that is what
will be stashed there, ending up with:
name = "/bin/\0"
last_slash---^
name = "/bin/ls.debug\0"
I.e. its not really the last slash, but where the debuglink content has
to be stashed, concatenating with the same dirname as the associated
binary.
Can you please rename "last_slash" to "debuglink"? And "path" to
"debuglink" as well in the routine that reads the debuglink.
> + size - (last_slash - name));
> + }
Other than that, thanks a lot for working on this, surely we have to
support this feature!
- ARnaldo
next prev parent reply other threads:[~2012-06-21 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 22:22 Pierre-Loup A. Griffais
2012-06-21 17:28 ` Arnaldo Carvalho de Melo [this message]
2012-06-21 18:41 ` Pierre-Loup A. Griffais
2012-06-22 12:39 ` Arnaldo Carvalho de Melo
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=20120621172859.GA17747@infradead.org \
--to=acme@ghostprotocols.net \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mikesart@valvesoftware.com \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=pgriffais@nvidia.com \
--cc=torvalds@linux-foundation.org \
/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
all inboxes | Powered by JetHome®