Hi Andrew,
I updated the README for ghc-debug last week but forget to send this mail!
https://gitlab.haskell.org/ghc/ghc-debug
Cheers,
Matt
On Wed, Jan 27, 2021 at 10:15 PM Andrew Kvapil wrote:
>
> Hello Ben,
>
> Thanks for your suggestions. The decision to adapt GHCi came out of a
> discus
Hello Ben,
Thanks for your suggestions. The decision to adapt GHCi came out of a
discussion with my supervisor and his colleagues. At this point the
entire set of desired capabilities of the work is still unknown, however
we do consider the GHCi-compatible programs to represent a large enough
set
Andrew Kvapil writes:
> Hello,
>
> I'm interested in inspecting the strictness of functions at runtime
> and the depth of thunks "in the wild."
Hi Andrew,
Interesting. When I first read your introduction my first thought was to
rather walk the "normal" heap using ghc-heap or, perhaps, the relat
> If so, that sounds pretty feasible. It might risk keeping variables
alive
> that would otherwise have been garbage-collected, but maybe that's a
price
> worth paying.
>
> Simon
>
>
> | -Original Message-
> | From: ghc-devs On Behalf Of Andrew
> |
Sent: 25 January 2021 11:06
| To: ghc-devs@haskell.org
| Subject: Inspecting function arguments in GHCi
|
| Hello,
|
| I'm interested in inspecting the strictness of functions at runtime
| and the depth of thunks "in the wild." For this reason I'm modifying
| GHC 8.10.
Hello,
I'm interested in inspecting the strictness of functions at runtime
and the depth of thunks "in the wild." For this reason I'm modifying
GHC 8.10.2, essentially to add additional information to breakpoints.
I'd like to reuse the logic behind GHCi's :print command
(pprintClosureCommand, obt
