Decode more StgTSO fields #41
Conversation
It now contains threadId and alloc_limit.
supersven
force-pushed
the
more_StgTSO_fields
branch
from
2b48173
to
090506d
Compare
Keep in sync with GHC wip/ghc-debug branch.
The stack closure changed.
Looks like the type of UI.mousemove changed.
Use a current artifact of wip/ghc-debug.
The extra package is not compatible to the current GHC head. Point cabal to a patched version.
The changes are mirrored from wip/ghc-debug.
…res types heap_view_closurePtrsAsWords is removed from GHC, so it needs to be defined in ghc-debug.
It's now patched in head.hackage.
| @@ -1,4 +1,4 @@ | |||
| packages: common, stub, client, dwarfadt, dwarf, ghc-vis, test, dyepack-test | |||
| packages: common, stub, client, dwarfadt, dwarf, ghc-vis, test, dyepack-test, test, /home/sven/src/head.hackage/packages/io-streams-1.5.1.0 | |||
There was a problem hiding this comment.
Getting things to build is one of my least favourite activities 😢 But I managed to figure out how to get this to build. I think you can get rid of this change and instead copy the head.hackage constraints (at least the one for io-streams) into this cabal.project file (this is described on the head.hackage page)
There was a problem hiding this comment.
Ups, Sorry!
/home/sven/src/head.hackage/packages/io-streams-1.5.1.0 is a left over from the time when I was waiting for my io-streams patch being merged to head.hackage. (https://gitlab.haskell.org/ghc/head.hackage/-/merge_requests/111)
There was a problem hiding this comment.
Ah great, so the head.hackage patch is already merged. Still though, when I did cabal new-build it selected the wrong io-streams version. Perhaps adding the constraints is not a bad idea (though maybe a separate PR).
There was a problem hiding this comment.
See here for more build instructions #42 (comment)
|
Hey @DavidEichmann , As soon as we solved all open issues on the ghc-debug branch (or at least all API changes), I'll update this branch. |
Stay in sync with the recent additions to
wip/ghc-debug.