public inbox for
 help / color / mirror / Atom feed
From: Christian Hergert <>
To: Serhei Makarov <>,
	builder--- <>
Cc: "Frank Ch. Eigler" <>, Mark Wielaard <>
Subject: Re: eu-stacktrace: roadmap and discussion thread
Date: Mon, 15 May 2023 10:55:40 -0700	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 5/11/23 12:27 PM, Serhei Makarov wrote:
> When the sysprof libraries are available, we could also use sysprof's
> mount namespace conversion code (in whatever eventual form it takes)
> to get .eh_frame data.

Is it correct that we won't get a PERF_EVENT_MMAP2 for all the processes 
already running when the profiler starts?

If so, do you have a strategy for how we would go extract `build-id` to 
insert into the capture file and/or prime eu-stacktrace?

-- Christian

  reply	other threads:[~2023-05-15 17:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08 12:33 Serhei Makarov
2023-05-08 21:50 ` Christian Hergert
2023-05-11 19:27   ` Serhei Makarov
2023-05-15 17:55     ` Christian Hergert [this message]
2023-05-09 18:02 ` Milian Wolff
2023-05-11 19:31   ` Serhei Makarov
2024-07-03 14:21 ` eu-stacktrace: roadmap update Serhei Makarov

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \

* 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).