It seems the OS X distribution is missing profiling libs, details at
https://gitlab.haskell.org/ghc/ghc/-/issues/20707 but that's basically
the whole story :)
___
ghc-devs mailing list
ghc-devs@haskell.org
http://mail.haskell.org/cgi-bin/mailman/listinfo/
Am 17/11/2021 um 17:08 schrieb Richard Eisenberg:
For windows we have Portable Executable (PE) as the container format.
This implies that the DWARF work is (unsurprisingly) completely inapplicable
for Windows.
It's not quite as simple. Dwarf info can be embedded into windows
executables/libra
Thanks for this!
> On Nov 17, 2021, at 7:27 AM, Moritz Angermann
> wrote:
>
> For Linux and most BSDs, we have settled on the Executable and Linking Format
> (ELF) as the container format for
> your machine code. And you might see where the inspiration for DWARF might
> come from.
This sugg
Thanks Carter!
Yes I completely forgot about the unwinding librarys.
Sorry. My bad!
Best,
Moritz
On Wed 17. Nov 2021 at 21:08, Carter Schonwald
wrote:
> My understanding is that the platform specific part of ghc dwarf support
> atm is the stack walking to generate dwarf data in stack traces.
My understanding is that the platform specific part of ghc dwarf support
atm is the stack walking to generate dwarf data in stack traces. This is
because the dwarf stack walking Libs that are relatively mature are mostly
centered around elf?
It should still be possible with some work to use perf a
Hi Richard,
I’m not sure using platform native AND the term DWARF would help rather
than add to confusion. Let me still try to
help a bit with context here.
For Linux and most BSDs, we have settled on the Executable and Linking
Format (ELF) as the container format for
your machine code. And yo
Hi devs,
I was intrigued by Bodigrim's comment about HasCallStack in base
(https://github.com/haskell/core-libraries-committee/issues/5#issuecomment-970942580)
that there are other alternatives, such as DWARF. Over the years, I had tuned
out every time I saw the word DWARF: it was (and is!) an
