exporting record_info (RE: Child modules draft feedback wanted)
Ulf Wiger (AL/EAB)
Fri Apr 7 10:00:00 CEST 2006
Mats Cronqvist wrote:
> using debug_info is cheating.
Indeed, and using debug_info on sites where
the source code is not available is ... non-trivial.
I was just replying to the observation that
record info were not available in the .beam
file. Under certain circumstances, they can be.
The debug_info can also be encrypted, and
decrypted on the fly. This can be used e.g.
to be able to include debug_info
and leave it throughout the testing. Then you
can release the beam code unchanged but without
the key that makes the debug info accessible.
More information about the erlang-questions