public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "Serhei Makarov" <serhei@serhei.io>
To: "Milian Wolff" <mail@milianw.de>,
	builder--- <elfutils-devel@sourceware.org>
Cc: "Frank Ch. Eigler" <fche@elastic.org>,
	"Mark Wielaard" <mark@klomp.org>,
	"Christian Hergert" <chergert@redhat.com>
Subject: Re: eu-stacktrace: roadmap and discussion thread
Date: Thu, 11 May 2023 15:31:04 -0400	[thread overview]
Message-ID: <de05c8b9-33e6-474c-aaf0-fb51e82ebe95@app.fastmail.com> (raw)
In-Reply-To: <3375729.uvHT6U3Wrp@milian-workstation>

On Tue, May 9, 2023, at 2:02 PM, Milian Wolff wrote:
> Hey Serhey,
>
> sounds like a fun project. If you want to see some prior art in that area, do 
> have a look at perfparser [1], esp. [2], and [3]. We solved quite a few of the 
> problems you might encounter in this area. Esp. for good performance, you'll 
> need quite a bit of caching on the stacktrace side, such as [4] and [5].
Excellent, I do look forward to finding out what kind of caching I'll need to implement,
and if your solutions work for our use case, then I think making them more
widely-available via elfutils would be a good outcome all round.

All the best,
     Serhei

  reply	other threads:[~2023-05-11 19:31 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
2023-05-09 18:02 ` Milian Wolff
2023-05-11 19:31   ` Serhei Makarov [this message]
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:
  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=de05c8b9-33e6-474c-aaf0-fb51e82ebe95@app.fastmail.com \
    --to=serhei@serhei.io \
    --cc=chergert@redhat.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=fche@elastic.org \
    --cc=mail@milianw.de \
    --cc=mark@klomp.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).