Mail Archives: djgpp/1993/12/22/04:14:34
> I think I figured out the Ctrl-Break bug, and it is go32's fault. To
> try the fix, replace the go_til_stop prototype in utils.h with one
It's mostly fixed .... ;-)
If you run Morten Welinder's (terra AT diku DOT dk) test program, the
original bug goes away, but another rears it's ugly head. I've got my
keyboard repeat set pretty high (18/sec?), and holding down Ctrl-Break
eventually causes GO32 to die with an "unsupported INT XXX" error (at
which point my PC is hosed and must be rebooted via the reset or power
switch). The "XXX" is usually "2F", but I've seen it be other
interrupts (0x0D? -- I'm not sure). Here's a screen dump from the one
time where my PC didn't crash:
-------------------------------------------------------------------------------
D>e:\djgpp\go32\go32t a.out
go32 version 1.11.maint1 Copyright (C) 1993 DJ Delorie
waiting and polling - press Ctrl-Break to step a counter,
any other key to go on, 's' to stop.
Ctrl-break was pressed 0 time(s).
Ctrl-break was pressed 0 time(s).
Ctrl-break was pressed 0 time(s).
Unsupported INT 0x2f
Exception 47 (0x2f) at eip=1762
eax=00000e08 ebx=0000f86c ecx=0000f84c edx=00001b1b esi=000012d2 edi=00000000
ebp=7ffff820 esp=7ffff810 cs=48 ds=48 es=48 fs=48 gs=48 ss=48 cr2=00009000
Call frame traceback EIPs:
0x00001762
Unsupported INT 0x0d
Unsupported INT 0x00 0x00000000
D>^C
-------------------------------------------------------------------------------
This is with go32 1.11maint with the proposed Ctrl-break patch.
Yes, I did recompile ALL of go32.
-- Darryl Okahata
Internet: darrylo AT sr DOT hp DOT com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion or policy of Hewlett-Packard or of the
little green men that have been following him all day.
- Raw text -