Linked by Thom Holwerda on Mon 7th Mar 2011 23:21 UTC
Permalink for comment 465713
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2010-05-19
*headdesk*
Such and investigation (of a single event) can be a multi-million dollar proposition, and still might not uncover the cause.
There are _numerous_ debugging tools out there, and I can do a memory dump, if I must.
Do it with processor emulator and I can step at any speed I choose, pause, and inspect the state.
If the software allows, I can use standard debugging tools and step through the execution.
Yowza, you're ignorant.