Reverse Engineering the Source Code from .gblorb

Gblorbs are not zip packages so that won’t work.

If it’s not too much trouble, would you mind submitting the revised executable to the IF Archive? It would be great to have an up-to-date version there.

I don’t think it’s quite ready yet. The thing is, running it on any gblorb now gives

mrifk: Mrifk_strings.hs:(99,5)-(102,30): Non-exhaustive patterns in case

This indicates that we probably have 0xe2 as a code somewhere. It appears to extract 32-bit data.

github.com/jcmf/glulx-strings/b … strings.py gives some insight as to how to do that. And in fact it is more useful cross-platform for text extraction because it is a webpage and not a compiled executable. But this might be neat to have for full disassembly.

I have a feeling we just need to add a few lines of code. l’ll see if I can translate the python into haskell. It loks like a good but nontrivial exercise.

1 Like