freenode/#clasp - IRC Chatlog
Search
4:11:07
beach
drmeister: It looks to me like SBCL uses the ordinary printer for printing backtraces, but then it handles any error and displays "error printing frame" instead.
5:11:58
drmeister
::notify Bike - I pulled cc_dispatch_miss and cc_dispatch_debug out of fastgf.cc and put them into link_intrinsics.cc. It builds again. Doing this drops the boehm-fastgf-cxx.ll file down to 654 lines but with them it is 12153 lines. This shouldn't cause a crash (dunno what's up there) but it's way too large to inline into every discriminating function. I was very careful to check boehm-fastgf-cxx.ll so make sure ...
5:13:42
drmeister
::notify Bike - ... it stayed as small as possible and didn't drag in a lot of other code, which is apparently what happens when we add cc_dispatch_miss and/or cc_dispatch_debug. These are slow path and debugging functions - and one or both cause a LOT of other code to get dragged in to boehm-fastgf-cxx.bc.
5:15:49
drmeister
beach: I can't seem to do anything that allocates memory via the GC when I'm debugging a crash. So I need a printer that doesn't cons at all.
11:53:26
drmeister
kpoeck: Thank you for the heads up on that fixup.lsp build problem yesterday. That would have been nasty today.
11:54:37
drmeister
Well, that's not quite fair - we got a docker build that built cleanly - so we could have used that.
11:55:49
kpoeck
I actually tried to do git reset to older commit, but obviously didn't go back long enough
11:56:19
drmeister
Sort of. I got the bullet proof backtrace to work just before we left. I was thinking about it as I drove. When I got to the hotel I checked a few things and noticed that the fastgf inline code was way bigger than I remembered it.
11:57:13
drmeister
Bike had moved it for logical reasons - I had forgotten how sensitive the fastgf stuff was to inline code size.