Hi, I'm trying to debug programs written for Hivemind. In order to catch the errors, I need to examine the variable contents within Hivemind during execution.
I use Eclipse 3.0. In my setup, I attach hivemind jars to the build path, set its javadoc and source paths properly. In a debug session, I can trace the hivemind code, step through it, put breakpoints, etc. However, for some reason, I can't see the variable contents. Eclipse gives me '<variable_name> cannot be resolved' message when I try to inspect a variable created locally inside a method. In the variables pane, I can see variables named 'this' and 'arg0, arg1, etc.'; in other words, I can see the class itself, and the variables passed to the parameter (although not with actual names, argN names instead). I try the same thing with other libraries, did this with servlet-api of Tomcat's and it worked. I can freely wander around vars inside the code. Why do you think this behaviour is so in Hivemind ? Do you think it has anything to do with its usage of proxies and bytecode enhancement libraries (javassist namely) ? And how do you debug Hivemind internals ? Best regards, Bulent Erdemir --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
