2007-01-04
(no subject)
Interesting.
My System.out.println() statements are printing only if I'm in the Eclipse debugger, and only if there's a breakpoint on the line containing them.
Some more digging shows that any println() statement that are before the call to CUP work, as long as I flush the output. Which implies that CUP (or possibly JFlex) is doing something evil to System.out.
Hmm, a full rebuild later and it works, for given values of work. Stupid race conditions between System.out and System.err, and a pox upon Java and Eclipse for doing weird things with buffering.
My System.out.println() statements are printing only if I'm in the Eclipse debugger, and only if there's a breakpoint on the line containing them.
Some more digging shows that any println() statement that are before the call to CUP work, as long as I flush the output. Which implies that CUP (or possibly JFlex) is doing something evil to System.out.
Hmm, a full rebuild later and it works, for given values of work. Stupid race conditions between System.out and System.err, and a pox upon Java and Eclipse for doing weird things with buffering.
(no subject)
As nice as Eclipse is, it doesn't half chew through memory. 280MB and counting before I restarted it to try and free some up (this machine only has 512MB of memory). Then again, it is a Java IDE written in Java and so completely out of control.
(no subject)
Anyone recognise bzq-82-80-249-146.dcenter.bezeqint.net (or similar)?
There's a rogue bot being run from there (and possibly other IP addresses in the same subnet) that's ignoring the rules. It claims to be "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; (R1 1.1); .NET CLR 1.1.4322)", but *real* web browsers also send user-agents for inline images.
The cheeky git chewed through a good 80MB of my bandwidth yesterday (running what looks like multithreaded and with no rate limiting), hence why I've noticed it.
There's a rogue bot being run from there (and possibly other IP addresses in the same subnet) that's ignoring the rules. It claims to be "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; (R1 1.1); .NET CLR 1.1.4322)", but *real* web browsers also send user-agents for inline images.
The cheeky git chewed through a good 80MB of my bandwidth yesterday (running what looks like multithreaded and with no rate limiting), hence why I've noticed it.