S-Lang Error

S-Lang Error

[Nicolai Kuntze]

Hi,

in my log is always this line:

Slang:S-Lang Error: Inconsistency in define key.

Can anyone tell me, what does it mean and if it is dangerous???

Btw. leavedos(0|0x0) is there a meaning for the numbers in the leavedos line? Can I determine an errorcode out of it?

Nicolai


---- 
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.

Re: S-Lang Error

[Bart Oldeman]

On Thu, 12 Feb 2004, Nicolai Kuntze wrote:

> in my log is always this line:
>
> Slang:S-Lang Error: Inconsistency in define key.
>
> Can anyone tell me, what does it mean and if it is dangerous???

It means a certain key escape code was defined strangely by DOSEMU.
Certainly not dangerous. Someday I'll have a look but it's not very
important.

> Btw. leavedos(0|0x0) is there a meaning for the numbers in the leavedos line?
> Can I determine an errorcode out of it?

Sometimes. If you have the source you know more quickly where DOSEMU
exited from. That's all really. 0 means success.

Bart

Re: S-Lang Error

[Nicolai Kuntze]

Am Do 12.02.2004 22:31, Bart Oldeman <bartoldeman@users.sourceforge.net> schrieb:

> On Thu, 12 Feb 2004, Nicolai Kuntze wrote:
> > Btw. leavedos(0|0x0) is there a meaning for the numbers in the leavedos line?
> > Can I determine an errorcode out of it?
> 
> Sometimes. If you have the source you know more quickly where DOSEMU
> exited from. That's all really. 0 means success.
> 
> Bart
> 

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? What does this code mean?

Nicolai


---- 
Diese Nachricht wurde auf Viren und andere gefaehrliche Inhalte sowie Spam untersucht.

Re: S-Lang Error

[Stas Sergeev]

Hello.

Nicolai Kuntze wrote:
> 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.

Re: S-Lang Error

[Nicolai Kuntze]

Am Fr 13.02.2004 22:22, Stas Sergeev <stsp@aknet.ru> schrieb:

> 
> Hello.
> 
> Nicolai Kuntze wrote:
> > 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.
> -

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.