1  |   Order by index

Jul 14, 2006, 6:01am

Is it me or was the ability to debug using the sdk a helpful thing? I think
it was a bad idea to disable it, being it helped developers to make
conclusions about their bugs.

Jul 14, 2006, 7:24am

SDK Build 62 appears to have this restriction removed (no 2 second exec time
on aw_init, stepping through code seems to work fine).

Assuming this wasn't an oversight (in which case it would have come to light
eventually anyway, so don't slap me for pointing it out should they put it
back in for Build 63+), its certainly good to have our development tools
back, and I for one am grateful for that decision!

I've just got to get my hands out of the CTRL-F5 habit now (but I think I'll
wait a while, to see if there's a restricted Build 63 on the way).

Grims.

[View Quote]

Jul 14, 2006, 12:47pm

Interesting, I get bombarded with lots of 'EclipseEvolution.exe has
triggered a breakpoint'

--
- Mark Randall
http://www.temporal-solutions.co.uk

"We're Systems and Networks..."
"It's our job to know..."

[View Quote]

Jul 14, 2006, 1:06pm

[View Quote] As I suspected, interupts originating from within the SDK

100C90A6 8B C0 mov eax,eax
100C90A8 CC int 3
100C90A9 C1 E8 08 shr eax,8

Im no good with LL interupts, so someone will have to enlighten me as to
what interupt 3 actually is on a Pentium system.

--
- Mark Randall
http://www.temporal-solutions.co.uk

"We're Systems and Networks..."
"It's our job to know..."

Jul 14, 2006, 8:00pm

Its the breakpoint interrupt. The SDK is littered with them.

-Joe

[View Quote]

Jul 15, 2006, 3:40am

[View Quote] Sucks, I smell the need for a kernel mode interupt filter :O

--
- Mark Randall
http://www.temporal-solutions.co.uk

"We're Systems and Networks..."
"It's our job to know..."

Jul 20, 2006, 7:28am

Now THAT's an idea. Then it doesn't matter if the SDK tries to scream
if it gets debugged, the interrupts won't get there. ^_^

-Lt


[View Quote]

1  |   Order by index