Silverfrost Forums

Welcome to our forums

SDBG error 128 with /undef

7 Jun 2011 1:51 #8358

Hi,

Quick piece of help, if anyone knows. I've got some code that runs OK when compiled without any debug switches, but if compiled with /undef, causes the debugger to close with a message:

'program has exited with a code 128'.

I'm sure the 128 is significant, but is it the same as the runtime error 128?

i.e. 'file does not exist'

or does it mean something different?

K

Please login to reply.