From: Mark Wielaard <mjw@redhat.com>
To: elfutils-devel@lists.fedorahosted.org
Subject: Re: [patch] Fix resolving ELF symbols for live PIDs with deleted files
Date: Fri, 29 Aug 2014 11:55:32 +0200 [thread overview]
Message-ID: <1409306132.4981.13.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: 20140828201216.GA2549@host2.jankratochvil.net
[-- Attachment #1: Type: text/plain, Size: 1355 bytes --]
On Thu, 2014-08-28 at 22:12 +0200, Jan Kratochvil wrote:
> Formerly shared libraries did not get resolved properly:
> #2 0x00007fc4d86c56d6
> #3 0x0000000000400938 main
>
> Fixed elfutils produce:
> #2 0x00007f61094876d6 libfunc
> #3 0x0000000000400938 main
>
> Signed-off-by: Jan Kratochvil <jan.kratochvil@redhat.com>
Nice, thanks. I would add the why to the commit message. "For deleted
shared library files the offsets to the symbol table were calculated
wrongly from the phdrs because the main_bias wasn't taken into account."
+2014-08-28 Jan Kratochvil <jan.kratochvil@redhat.com>
> +
> + * dwfl_module_getdwarf.c (find_offsets): Add parameter main_bias, use
> + it.
> + (find_dynsym): Pass the new parameter main_bias.
>
Looks good.
+# Older Linux (such as 2.6.32) required PTRACE_ATTACH to read /proc/PID/mem.
> +sleep 60 & p=$!; sleep 0.1
> +addr=0x$(cat /proc/$p/maps|sed -n 's#^\([0-9a-f]*\)-[0-9a-f]* r[^ ]* 00* .*/sleep$#\1#p'|head -n1)
> +supported=$[$(dd if=/proc/$p/mem bs=1 skip=$[$addr] count=1|wc -c)]
> +kill -9 $p
> +if [ $supported -eq 0 ]; then
> + exit 77
> +fi
I don't think this check is needed. eu-stack needs to be attached to get
the register values and dwfl_linux_proc_find_elf makes sure the process
is attached before calling elf_from_remote_memory.
Cheers,
Mark
next reply other threads:[~2014-08-29 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 9:55 Mark Wielaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-08-29 21:00 Mark Wielaard
2014-08-29 20:44 Mark Wielaard
2014-08-29 20:38 Jan Kratochvil
2014-08-29 20:15 Jan Kratochvil
2014-08-28 20:12 Jan Kratochvil
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=1409306132.4981.13.camel@bordewijk.wildebeest.org \
--to=mjw@redhat.com \
--cc=elfutils-devel@lists.fedorahosted.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).