[DGD] Control block dumping
Raymond Jennings
shentino at gmail.com
Mon Dec 10 01:37:13 CET 2018
I would like to know if there's a viable way to dump a control block to,
say, stderr or a file or something in human readable form.
I can definitely reverse engineer this from the source, but it would be
useful to be prepared with a few hints or tips.
Example:
A list of all the variables and their types
A list of all functions and their prototypes (what their return value is,
what arguments they take)
A list of all their inherits
Purpose:
General debugging, and I also have a statedump that I'd like to audit for
conformity to the source code. I'm curious if the compiled bytecode and
corresponding prototypes actually match up with what's defined in the LPC
source.
I have reason to suspect the admin in charge of this particular statedump
has been less than diligent about recompiling changed source and I also
noticed traces of precompile helpers.
I can't divulge much in the line of specifics as I'm under an NDA.
More information about the DGD
mailing list