Today's mainframeanything to new 556
Actually, both are often highly related and can only be fixed by watching both at the same time.
Charles Shannon Hendrix) writes: Either that or (in the case of my Win98 box), the memory...
Depends on the system in question of course.
Not if you always run performance monitoring. That's what a lot of people do, and for exactly the problem you mention.
Yep. Either that, or problems that debugging affects.
One fun one in UNIX is when you use memory that had been deallocated, or is otherwise off-limits. Sometimes when debugging, the program will work fine because you end up flushing I-O buffers which need that memory before it goes completely out of scope (what that means exactly depends on the system below). Run at normal speed and you get an error.
It's really frustrating but when you notice this behavior, you are almost garanteed to have just narrowed down the problem. Sometimes it can take awhile to realize the cause, but once you have, finding the offender is usually pretty quick.
Of course there is measurement and security overhead; but you are in error about performance and security monitoring being contrary. They are different views of the same observations. The challenge is to build...
Sometimes debugging hides bugs instead of finding them, but it is still useful information.
In most shops I've been in, I don't see many people using debuggers.
Even the Java programmers, who are usually using IDEs with very exensive debugging systems, seem to rarely use them.
-- shannon "AT" widomaker.com -- "All of us get lost in the darkness, dreamers turn to look at the stars" -- Rush
----== Posted via Newsfeeds.Com - Unlimited-Uncensored-Secure Usenet News==---- ----= East and West-Coast Server Farms - Total Privacy via Encryption =----
Today's mainframeanything to new 557
Alt Folklore Computers from Newsgroups