Comments on: Eclipse Part 2 http://blog.xcski.com/2008/06/04/eclipse-part-2 Everything I used to bore people on newsgroups and mailing lists with, now in one inconvenient place. Tue, 02 Dec 2008 05:30:19 +0000 http://wordpress.org/?v=2.6.5 By: Paul Tomblin http://blog.xcski.com/2008/06/04/eclipse-part-2#comment-93041 Paul Tomblin Wed, 04 Jun 2008 19:40:16 +0000 http://blog.xcski.com/?p=1368#comment-93041 I haven't had much luck figuring out how to make Eclipse watch a variable. So far I've used it to break at particular places in the code and on exceptions only. On the other hand, I've been bitten by code where adding print statements caused the problem to go elsewhere. I haven’t had much luck figuring out how to make Eclipse watch a variable. So far I’ve used it to break at particular places in the code and on exceptions only.

On the other hand, I’ve been bitten by code where adding print statements caused the problem to go elsewhere.

]]> By: David Parsons http://blog.xcski.com/2008/06/04/eclipse-part-2#comment-93039 David Parsons Wed, 04 Jun 2008 18:36:25 +0000 http://blog.xcski.com/?p=1368#comment-93039 Maybe you'd been bitten by a debugger that claimed to be able to watch variables, but doesn't actually do so? That's one big feature of not working in a pmachine; debuggers will cheerfully let you set watchpoints on a variable, but will then ignore array overflows, stack crunches, or unexpected aliasing, leaving you muttering curses on the ancestry of the debugger, the compiler, and the hardware it rode in on. (On the bright side, having to printf() code into submission and then single-stepping through a network daemon is a /very/ good way to convince oneself to start coding in a far more paranoid manner.) Maybe you’d been bitten by a debugger that claimed to be able to watch variables, but doesn’t actually do so? That’s one big feature of not working in a pmachine; debuggers will cheerfully let you set watchpoints on a variable, but will then ignore array overflows, stack crunches, or unexpected aliasing, leaving you muttering curses on the ancestry of the debugger, the compiler, and the hardware it rode in on.

(On the bright side, having to printf() code into submission and then single-stepping through a network daemon is a /very/ good way to convince oneself to start coding in a far more paranoid manner.)

]]>