I think that would be a splendid idea. When I was playing with big bank (which I hope to get back to shortly) I ended up using the SDOUtils:printDataObject() method at strategic points in the code. As you say it's very difficult to tell what's going on in GDB.
Regards Simon On 8/7/06, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
I'm finding SDO DataObjects a little difficult to inspect with the GDB debugger. Is there anything that could be done to help debuggers display the contents of SDO DataObjects, properties and types? Just an idea... but would it make sense to add to SDO DataObject a string member containing its serialized contents, only when compiled with the debug option maybe... Would that help? Any thoughts? -- Jean-Sebastien --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
