Mail Archives: djgpp/1994/12/26/10:21:45
> Is there a way to make go32 print a stack trace on purpose? It does it
> when something goes wrong, can I do it by calling some function or
> other? It seems like it might be useful for letting me know how a
> program got into a sticky situation. I'm pretty sure I'll never use it,
> but it just occured to as something that might come in handy sometime. :)
A couple of things to try:
asm("int $3");
*(int *)(-1) = 0;
These cause various faults that in turn cause stack dumps or debugger
traps (the first one *is* a debugger trap).
- Raw text -