S-Lang Error
Hello.
Quoted 1 line · Nicolai Kuntze
I've browsed the source, but after this I'm not further then before. I have a leavedos(1|0x1) and I think I get this every time the execution of the program in the box failes. Can I switch on some debugging to get a closer look on this?
The best way to investigate the source of leavedos() call would be to compile dosemu with debug info, start it under gdb and, setting the break-point to leavedos(), produce a stack trace when that break-point is reached.
Quoted 8 lines · Stas Sergeev
Hello.
Quoted 4 lines · Nicolai Kuntze
I've browsed the source, but after this I'm not further then before. I have a leavedos(1|0x1) and I think I get this every time the execution of the program in the box failes. Can I switch on some debugging to get a closer look on this?
Quoted 8 lines
The best way to investigate the source of
leavedos()call would be to compile dosemu with debug info, start it under gdb and, setting the break-point toleavedos(), produce a stack trace when that break-point is reached.
-
I am unexperienced in such things and so I have never used gdb before. So, here some, possibly stupid, questions:
Is it possible to automate this. The error occurs from time to time, but without any resonably pattern. This in mind, I need a way to always start the debugger but only to record the crash.
Thanks for your help.
Nicolai
----
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.