Option 1 (Current): Dev adds wrappings for arguments that they think look interesting, in a format that suits. This allows for handy custom formats like "RWX" instead of "0x40".
If it's not already there then you need to request it or write+build it yourself. Distribution of your fancy wrapping code would have to be in the form of source (pain in the neck) or binary (what could go wrong).
Option 2: The client reads in an optional user-supplied text file for each library it loads. It reads symbols, arguments required from each symbol and the format of each argument.
Pros- Easy to contribute to, customise for individual binaries and safe to distribute.
Cons- Does nothing more than return the argument. No custom processing code.
Option 3: Option 1 [unless an option 2 file exists]
Option 1 (Current): Dev adds wrappings for arguments that they think look interesting, in a format that suits. This allows for handy custom formats like "RWX" instead of "0x40".
If it's not already there then you need to request it or write+build it yourself. Distribution of your fancy wrapping code would have to be in the form of source (pain in the neck) or binary (what could go wrong).
Option 2: The client reads in an optional user-supplied text file for each library it loads. It reads symbols, arguments required from each symbol and the format of each argument.
Pros- Easy to contribute to, customise for individual binaries and safe to distribute. Cons- Does nothing more than return the argument. No custom processing code.
Option 3: Option 1 [unless an option 2 file exists]
Option 4: ???