Mail Archives: djgpp-workers/2002/05/14/15:34:11
> That's what puzzles me: the Emacs code plays it so safe that I don't
> know where to start looking for possible problems. It uses only
> standard video modes, goes through BIOS for keyboard input, and reads
> the mouse via Int 33h. Direct screen access through dosmemput,
> dosmemget, and ScreenRetrieve is about the most ``fancy'' code you
> will see there.
Windows 2000 is no DOS, so IMHO 'plays it so safe' is something else,
namely, how good w2k virtualization/emulation of some feature is, no
matter how 'nice' or 'good' that feature is in the real DOS...
OK, enough of theories, here is one checkpoint i've hit:
------8<-----------------------------------
--DD\---F1 *scratch* (Lisp Interaction)--L5--All-----------------------
M-x tetris
Breakpoint 1, Fexecute_extended_command (prefixarg=270752772)
at keyboard.c:9314
9314 real_this_command = function;
(gdb) n
9317 if (!NILP (Vsuggest_key_bindings)
(gdb)
9320 bindings = Fwhere_is_internal (function, Voverriding_local_map,
(gdb)
D:\devel\djgpp\gnu\emacs\BIN>
------8<----------------------------------
Now that keyboard.c:9320 line is the one causing aborts every time.
I'll dig further now. I'm sending this just to check it it doesn't
ring any bell to you?
Laurynas
- Raw text -