Am Fr., 19. Nov. 2021 um 01:09 Uhr schrieb Ben Gamari :
> Artem Pelenitsyn writes:
>
> > Another question would be where do I read about Haskell-native stack
> > unwinder. The issue and MR Ben referenced have descriptions, but the MR
> > didn't touch anything inside `docs` which is a bit scary.
Artem Pelenitsyn writes:
> Another question would be where do I read about Haskell-native stack
> unwinder. The issue and MR Ben referenced have descriptions, but the MR
> didn't touch anything inside `docs` which is a bit scary. Are there any
> good recourses to dive into it besides the source
Hi Norman,
Could you see if the command-line described here is of any help?
https://gitlab.haskell.org/ghc/ghc/-/issues/17929#building-the-docs
Particularly the "--freeze1 --flavour=Quick" bit.
Cheers!
Le 18/11/2021 à 21:06, Norman Ramsey a écrit :
In service of #20528, I'm trying to clean
In service of #20528, I'm trying to clean up some Haddock
documentation in the GHC sources. The only command I know is
./hadrian/build -j _build/docs/html/index.html
It turns out that if I change Haddock comments in one file
(GHC/Tc/Gen/Foreign.hs), rebuilding the HTML takes a minute
and a
Another question would be where do I read about Haskell-native stack
unwinder. The issue and MR Ben referenced have descriptions, but the MR
didn't touch anything inside `docs` which is a bit scary. Are there any
good recourses to dive into it besides the source code in the MR?
--
Best, Artem
On
Just to satisfy my curiosity here, when talking about backtraces here, are
you talking about a lexical call stack, or an execution stack?
On Thu, Nov 18, 2021 at 11:24 AM Richard Eisenberg
wrote:
>
>
> On Nov 18, 2021, at 10:29 AM, Ben Gamari wrote:
>
> At this point, for backtrace support I
> On Nov 18, 2021, at 10:29 AM, Ben Gamari wrote:
>
> At this point, for backtrace support I would rather put my money is on a
> native Haskell stack unwinder (such as Sven Tennie's work [3,4]). Not only
> is it more portable but it is also more robust (whereas with DWARF any
> single object
Richard Eisenberg writes:
> 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
Richard Eisenberg writes:
> 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
