Hi Serhei,
On Wed, Aug 20, 2025 at 6:12 PM Serhei Makarov wrote:
>
> Hello,
>
> I've been concerned to get libdwfl_stacktrace out of the weird 'experimental'
> limbo we put it in for the last elfutils release. To do that, we need to
> stabilize the API.
>
> My full prototype of a more mature AP
Here is some additional data showing how the performance scales on
larger binaries. I used the exact same set up as I described in the
previous email, only replacing the 64M stap binary with firefox's 1G
libxul.so.debug:
$ hyperfine --runs 5 -i --warmup 2 'eu-readelf -C1 -N -w libxul.so.debug'
th
Initial response from what I know, pending being actually sure about the
answers.
On Wed, Sep 3, 2025, at 9:51 AM, Mark Wielaard wrote:
> Could you explain again why we have the first set of arguments?
> Dwfl *dwfl, Elf *elf, pid_t pid, pid_t tid
> Some of this seems a little repetitive. Ideall
Hi Serhei,
On Wed, 2025-08-20 at 18:12 -0400, Serhei Makarov wrote:
> The header-only patch below illustrates the planned API change.
> The base solution is for dwflst_sample_getframes() to take a pointer
> to regs_mapping, which, for each item in regs[] array, specifies its
> position in the full
