Mail Archives: djgpp/2001/05/09/15:34:20
There was no change in the behavior. GDB was also killed when Emacs
aborts.
I will try to recompile Emacs with the debug info, to catch up the
keyboard input routine.
_______ ()()())
____ (_______) /\ ()( ( ) ())
(__ )_ ________||___ ( ( ) (( ) ()
(___) __ / \ || \ ( )( ) ) () )
____ (__) / _ \ \ () ( ) () )
(____) / |_| \ \ ()(()() ()
/| _ |\___________\ | | (()(()
___ ~~-_ | | | | |__| |__| | | | (())
(___) _||____ _____|_|_|_|___________|______/___\_________||__
___________\_____/______/ Eduardo Andres Espinoza Espinoza
~ ~ ~ ~ ~ / eespinoz AT puc DOT cl, eespinoz AT ing DOT puc DOT cl
On Wed, 9 May 2001, Eli Zaretskii wrote:
> > Date: Wed, 9 May 2001 12:22:34 -0400
> > From: "Eduardo Espinoza E." <eespinoz AT ing DOT puc DOT cl>
> >
> > Habitually i use cmd.exe. In this case, when Emacs aborts (according
> > to your indication), the prompt appear one line under the last place of
> > the cursor (the screen is not cleared).
>
> This is expected: the code which clears the screen only runs upon
> normal exit.
>
> > Also i verified that if Emacs is executed as a child process, the
> > parent (a DJGPP program that i create to test this situation) whas also
> > silently finished when the problem appears.
>
> That's really bad, it means that it will be very hard to find the
> reason. Can run Emacs under GDB, and see if it behaves differently in
> any way?
>
- Raw text -