It appears that the Sun JDK really sucks in debug mode. I was running it with -Xdebug -Xnoagent -Xrunjdwp transport=dt_socket,server=y,address=7 777,suspend=n -mx400m freenet.node.Main , so that I could connect to it with eclipse. It is only using one process, so presumably it is using green threads in order to make pausing the whole JVM possible. However every time I try to go to any freesite, it eventually returns 0 data, the logfile for the last hour (I haven't bothered to unzip previous hours) contains only about 5 different messages, repeated over an over (attached, gzipped), and when I get a stack dump, twice, I find many threads waiting for the Ticker and the Ticker waiting for a lock on "<0x460d05e8> (a freenet.support.BufferLoggerHook)", which is apparently not locked by ANY thread. I would have just written this down to stack dumps not being atomic except a) it's running in debug mode, and using green threads, apparently, so they probably are atomic, and b) I got two separate stack traces several seconds apart that said exactly the same thing.
Debugging Fred in Eclipse is therefore much harder than originally thought. I will revert to my usual shotgun debugging approach. -- Matthew J Toseland - [EMAIL PROTECTED] Freenet Project Official Codemonkey - http://freenetproject.org/ ICTHUS - Nothing is impossible. Our Boss says so.
signature.asc
Description: Digital signature
_______________________________________________ Devl mailing list [EMAIL PROTECTED] http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
