[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: C-g does not interrupt lisp code (emacs 21)
From: |
Richard Stallman |
Subject: |
Re: C-g does not interrupt lisp code (emacs 21) |
Date: |
Thu, 25 Oct 2001 09:22:49 -0600 (MDT) |
In my experience, tracing system calls is not a very effective
debugging method. I don't know why people use it except that they may
have got used to not having debugging symbols. The effective way to
find out what a program is doing when it won't exit a loop is to
compile it with -g and step through the loop under a debugger. That
way you will really see what is happening.
In general, if you are a programmer and you hesitate to run a program
under a debugger to diagnose the problem, the best single way you can
develop your skills is to learn to love the debugger.
- C-g does not interrupt lisp code (emacs 21), Philippe Waroquiers, 2001/10/24
- Re: C-g does not interrupt lisp code (emacs 21), Gerd Moellmann, 2001/10/24
- Re: C-g does not interrupt lisp code (emacs 21), Philippe Waroquiers, 2001/10/24
- Re: C-g does not interrupt lisp code (emacs 21), Gerd Moellmann, 2001/10/25
- Re: C-g does not interrupt lisp code (emacs 21), Philippe Waroquiers, 2001/10/25
- Re: C-g does not interrupt lisp code (emacs 21), Gerd Moellmann, 2001/10/25
- Re: C-g does not interrupt lisp code (emacs 21), Richard Stallman, 2001/10/28
- Re: C-g does not interrupt lisp code (emacs 21), Philippe Waroquiers, 2001/10/29
- Re: C-g does not interrupt lisp code (emacs 21),
Richard Stallman <=
- Re: C-g does not interrupt lisp code (emacs 21), Richard Stallman, 2001/10/25
- Re: C-g does not interrupt lisp code (emacs 21), Philippe Waroquiers, 2001/10/25
Re: C-g does not interrupt lisp code (emacs 21), Eli Zaretskii, 2001/10/24