Doesn't seem to matter what the CPU is, PCem crashes while booting Windows 98 and Windows Me. There's nothing in the log that shows more than a truncated "Create texture". I wish I had more info to give
Win95 and 2K are fine. I believe today's changes had regressed this since this config worked yesterday.
Here's a config where it happens. HDC contains a stock Win98SE installation without any updates/patches besides DX7 and 3dfxV2 drivers.
(Starting PCem through GDB hasn't worked for me since the new GUI got merged. If this also causes problems, try starting the emulator, then attaching GDB to it with --pid)
I've tried to make a debug build (though it seems to be failing to make the symbols) and attached gdb to its pid and I don't think it produces much useful info when it crashes at that point.
[New Thread 4152.0x11a4]
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4152.0xa7c]
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
0x00000001 in ?? (warning: (Internal error: pc 0x1 in read in psymtab, but not i
n symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
331 ../../include/wx/xrc/xmlreshandler.h: No such file or directory.
in ../../include/wx/xrc/xmlreshandler.h
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
(gdb) continue
Continuing.
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
Program received signal SIGSEGV, Segmentation fault.
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
0x00000001 in ?? (warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
331 in ../../include/wx/xrc/xmlreshandler.h
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
(gdb) continue
Continuing.
warning: (Internal error: pc 0x0 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
Program exited with code 030000000005.
(gdb)
) at ../../include/wx/xrc/xmlreshandler.h:331
#1 0x005435ad in ?? ()
#2 0x0054e234 in ?? ()
#3 0x0054c358 in ?? ()
#4 0x0055ca4a in ?? ()
#5 0x004270e2 in ?? ()
#6 0x00402082 in ?? ()
#7 0x0057143e in ?? ()
#8 0x00668ca1 in ?? ()
#9 0x6c7c3cf9 in SDL_LogCritical () from D:\PCemd\SDL2.dll
#10 0x00000000 in ?? ()
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
(gdb)
That looks like a potentially useful backtrace; pity there aren't any symbols!
If you can't get a build with symbols, could you send me the binary that generated that backtrace? I may be able to figure out what's going on from that.
Thanks for sending me the binary. I'm guessing though that it isn't the same build that you generated the above backtrace with, as none of the addresses match. Could you post a backtrace from the binary you've sent me?
(gdb) backtrace
#0 0x00000001 in ?? (warning: (Internal error: pc 0x1 in read in psymtab, but n
ot in symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
#1 0x00000002 in ?? (warning: (Internal error: pc 0x1 in read in psymtab, but n
ot in symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
#2 0x00000001 in ?? (warning: (Internal error: pc 0x0 in read in psymtab, but n
ot in symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
#3 0x00000000 in ?? ()
(gdb) continue
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00000001 in ?? (warning: (Internal error: pc 0x1 in read in psymtab, but not i
n symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
331 in ../../include/wx/xrc/xmlreshandler.h
(gdb) backtrace
#0 0x00000001 in ?? (warning: (Internal error: pc 0x1 in read in psymtab, but n
ot in symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
#1 0x00000002 in ?? (warning: (Internal error: pc 0x1 in read in psymtab, but n
ot in symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
#2 0x00000001 in ?? (warning: (Internal error: pc 0x0 in read in psymtab, but n
ot in symtab.)
) at ../../include/wx/xrc/xmlreshandler.h:331
#3 0x00000000 in ?? ()
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
(gdb) continue
Continuing.
warning: (Internal error: pc 0x1 in read in psymtab, but not in symtab.)
Program exited with code 030000000005.
(gdb) backtrace
No stack.
(gdb)
Sorry about that earlier. I had to update to check out the timing stuff for the slower parts.
Could you send me the NVR file you're using? I'm suspecting something may have got screwed up in the BIOS configuration telling Windows that there's more than 2 floppy drives.
Okay though i don't expect this to be different from the previous NVR file I posted. I only have the 3.25 on the bios and config and didn't set this Windows up on two floppy drives. (none of my configs use the default dual 2.88mb config/setup)
I've finally been able to reproduce this! Fix in rev 1019.
For the record, what is happening is that an unidentified driver (possibly for a tape streamer?) is executing commands on a non-existent drive 3, and does not handle unexpected FDC behaviour very well.