DOS ain't dead - SnglFault ->DblFault ->TripleFault -> BOOM

SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? (Developers)

posted by DOS386, 19.02.2008, 02:00

The "question" remains, why it crashes. Investigated and found the bug. :clap: BTW, I'm sure you are aware of this bug, since it becomes desperately obvious with your DEBUG version of DPMILD32 :lol3:

BOCHS wrote:

00000000000i[APIC?] local apic in initializing ======================================================================== Bochs x86 Emulator 2.3.6 Build from CVS snapshot, on December 24, 2007 ======================================================================== 00000000000i[ ] x86-64 support: yes 00264455460e[CPU0 ] write_virtual_checks(): write beyond limit, r/w 00264455460e[CPU0 ] can_push(): esp=0, normal, wraparound? limit=ffffefff 00264455460e[CPU0 ] can_push(): esp=0, normal, wraparound? limit=ffffefff 00264455460i[CPU0 ] CPU is in protected mode (active) 00264455460i[CPU0 ] CS.d_b = 32 bit 00264455460i[CPU0 ] SS.d_b = 32 bit 00264455460i[CPU0 ] EFER = 0x00000000 00264455460i[CPU0 ] | RAX=0000000000100000 RBX=0000000000000000 00264455460i[CPU0 ] | RCX=0000000000000002 RDX=0000000000002007 00264455460i[CPU0 ] | RSP=0000000000000000 RBP=000000000000005c 00264455460i[CPU0 ] | RSI=0000000000000020 RDI=00000000ffc01f14 00264455460i[CPU0 ] | R8=0000000000000000 R9=0000000000000000 00264455460i[CPU0 ] | R10=0000000000000000 R11=0000000000000000 00264455460i[CPU0 ] | R12=0000000000000000 R13=0000000000000000 00264455460i[CPU0 ] | R14=0000000000000000 R15=0000000000000000 00264455460i[CPU0 ] | IOPL=3 id vip vif ac vm RF nt of df if tf sf zf af pf cf 00264455460i[CPU0 ] | SEG selector base limit G D 00264455460i[CPU0 ] | SEG sltr(index|ti|rpl) base limit G D 00264455460i[CPU0 ] | CS:0020( 0004| 0| 0) ff801000 00006763 0 1 00264455460i[CPU0 ] | DS:0028( 0005| 0| 0) 0002bdb0 000ffffe 1 1 00264455460i[CPU0 ] | SS:0028( 0005| 0| 0) 0002bdb0 000ffffe 1 1 00264455460i[CPU0 ] | ES:004b( 0009| 0| 3) 00000000 000fffff 1 1 00264455460i[CPU0 ] | FS:0000( 0000| 0| 0) 00031040 0000ffff 0 0 00264455460i[CPU0 ] | GS:0000( 0000| 0| 0) 0002a6c0 0000ffff 0 0 00264455460i[CPU0 ] | MSR_FS_BASE:0000000000031040 00264455460i[CPU0 ] | MSR_GS_BASE:000000000002a6c0 00264455460i[CPU0 ] | RIP=0000000000004be5 (0000000000004be5) 00264455460i[CPU0 ] | CR0=0x80000031 CR1=0x0 CR2=0x0000000000000000 00264455460i[CPU0 ] | CR3=0x01fff000 CR4=0x00000200 00264455460i[CPU0 ] >> push ecx : 51 00264455460e[CPU0 ] exception(): 3rd (12) exception with no resolution, shutdown status is 00h, resetting 00264455460i[SYS ] bx_pc_system_c::Reset(SOFTWARE) called 00264455460i[CPU0 ] cpu software reset 00264455460i[APIC0] local apic in CPU 0 initializing 00264459200i[BIOS ] $Revision: 1.166 $ $Date: 2006/08/11 17:34:12 $

TripleFault inside HDPMI32 triggered by stack flooding :lol3:

DPMIST32.BIN and DPMILD32.EXE run each-other many times and flood HDPMI32's stack this way ... and the only way out preventing this crazy game from running into the infinity is the TripleFault :lol3:

IIRC we had the very same bug recently because of a bug in INFOPAD and "paranoid" DOS/32A :no:

But it comes even worse: Obviously DPMILD32 indeed activates the LOOOOOOOOOONG MODE :lol: !!!

I see 2 pieces that need fixing:

- DPMILD32: (don't load DPMIST32.BIN, + other issues, see other (soon) thread)
- HDPMI32: protect from Ring0 stack overflow

---
This is a LOGITECH mouse driver, but some software expect here
the following string:*** This is Copyright 1983 Microsoft ***

Post reply

Complete thread:

[BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - DOS386, 24.01.2008, 02:21 (Developers)
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - Japheth, 24.01.2008, 06:05
  - since it works perfectly .. never change a running system ? - DOS386, 19.02.2008, 01:41
    - since it works perfectly .. never change a running system ? - Japheth, 19.02.2008, 19:21
      - since it works perfectly .. never change a running system ? - DOS386, 20.02.2008, 01:45
        since it works perfectly .. never change a running system ? - Japheth, 20.02.2008, 08:16
        since it works perfectly .. never change a running system ? - Japheth, 21.02.2008, 10:22
  - SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - DOS386, 19.02.2008, 02:00
    - SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - Japheth, 20.02.2008, 10:51
      - SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - DOS386, 21.02.2008, 02:33
        SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - Japheth, 21.02.2008, 07:05
        SnglFault ->DblFault ->TripleFault -> BOOM - unavoidable ? - DOS386, 22.02.2008, 03:09
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - Laaca, 24.01.2008, 07:33
- [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - rr, 24.01.2008, 08:18
  - [BUG] Criminal Mark-related bug | DPMIST32.BIN/PESTUB/ VALX - DOS386, 19.02.2008, 01:30