Skip to contentSkip to conversation

Problems with Dosemu-1.1.3-Patchset 5

DISCUSSION Stas Sergeev 2 participants 2 messages Oct 14, 2002

lore
Share & tools
lore
#0 lore raw

Hello.

Quoted 3 lines · Bart Oldeman

could you check dosemu.map to see where 0x401ace06 is?
It might just be out of DOSEMU's scope; in that case it might be a DPMI page fault

Current buggy fault handler (to be fixed with my fault handling patch) have this:
if (in_dpmi)
return dpmi_fault(scp).

So, while it is a bug, if DPMI is active, there seems to be no way to reach that msg at all.
So I would say this is a buffer overflow most likely, and DPMI is disabled. gdb might help. This all will be much easier if I get around to implement the automatic gdb dispatcher, but for now you told there is another buffer overflow in mfs, isn't it?

#1 lore raw
Quoted 9 lines · Stas Sergeev
Quoted 3 lines · Bart Oldeman

could you check dosemu.map to see where 0x401ace06 is?
It might just be out of DOSEMU's scope; in that case it might be a DPMI page fault

Current buggy fault handler (to be fixed with my fault handling patch) have this:
if (in_dpmi)
return dpmi_fault(scp).

Quoted 9 lines

So, while it is a bug, if DPMI is active, there seems to be no way to reach that msg at all.
So I would say this is a buffer overflow most likely, and DPMI is disabled. gdb might help. This all will be much easier if I get around to implement the automatic gdb dispatcher, but for now you told there is another buffer overflow in mfs, isn't it?

No, that's what *you* suspected. I simply don't know. But if it would crash in the MFS code the page fault would occur for a different eip (at least with my dosemu.map).

We'll see.

Bart