public inbox for libc-help@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Abhijit Ray Chaudhury <abhijit.ray.chaudhury@gmail.com>
Cc: Abhijit Ray Chaudhury via Libc-help <libc-help@sourceware.org>
Subject: Re: Does glibc support remote process backtracing
Date: Mon, 11 Dec 2023 10:14:05 +0100	[thread overview]
Message-ID: <87bkaxt82q.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAACKNgV_XtTMiWy-HtQJvwaBTeappLERGtcYh6bxC4LafD7o7g@mail.gmail.com> (Abhijit Ray Chaudhury's message of "Tue, 28 Nov 2023 13:05:46 +0530")

* Abhijit Ray Chaudhury:

> Hi Florian,
>
> Thanks a lot for replying. I need to do remote stack tracing , for which I am using libunwind-ptrace
> . The problem is it does not work on VDSOs . It treats VDSO memory mapping entry in
> /proc/<pid>/maps as a file and tries to open it and subsequently fails.
> I tried mailing in libunwind-dev, but it seemed dormant .
>
> I need a library which works on both arm and x86_64 , do you think elfutils would be a good option
> ?

The AArch64 vDSO did not have accurate unwinding information in the
past.  We've got a Fedora bug for this:

  kernel: vDSO lacks unwind information on aarch64
  <https://bugzilla.redhat.com/show_bug.cgi?id=2044483>

I don't know if this has been fixed since then.

Thanks,
Florian


  reply	other threads:[~2023-12-11  9:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-25  6:02 Abhijit Ray Chaudhury
2023-11-27  9:20 ` Florian Weimer
2023-11-28  7:35   ` Abhijit Ray Chaudhury
2023-12-11  9:14     ` Florian Weimer [this message]
2023-12-11 15:50       ` Szabolcs Nagy

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=87bkaxt82q.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=abhijit.ray.chaudhury@gmail.com \
    --cc=libc-help@sourceware.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).