From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Emacs 21.2 - Garbage collector frenzy :-)
Date: Mon, 22 Apr 2002 10:23:46 +0300 (IDT) [thread overview]
Message-ID: <Pine.SUN.3.91.1020422101615.11473L-100000@is> (raw)
In-Reply-To: <oq8z7g7cld.fsf@titan.progiciels-bpi.ca>
On 21 Apr 2002, =?iso-8859-1?q?Fran=E7ois?= Pinard wrote:
> This is with Emacs 21.2 that I thought about checking if the problem is
> related to garbage collection, but I remember having observed such CPU
> loops in the latest pretest before 21.2, without much to say about them at
> the time. Not that I have so much more to say now... How could I proceed
> towards better reporting the problem?
Try this:
- Run Emacs under GDB. Be sure to start GDB from the `src' directory
of the Emacs source tree, to make it use the .gdbinit file with all
the additional commands it defines.
- When the problem happens, interrupt Emacs with "kill -TSTP PID",
where PID is the Emacs process ID, or by typing "C-c" at the window
where Emacs is run under GDB. This should cause GDB to kick in.
- At the GDB prompt, type "xbacktrace". It should produce the
Lisp-level backtrace showing what function caused the massive GC.
- Still at the GDB prompt, type "bt" for the C-level backtrace.
- Repeat the above 3 steps several times, each time continuing Emacs
after producing the backtraces. After that, you should have enough
information to figure out what feature(s) causes the massive GC.
Post that info here.
The file etc/DEBUG in the Emacs distribution has more hints for debugging
Emacs.
next prev parent reply other threads:[~2002-04-22 7:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-22 1:21 Emacs 21.2 - Garbage collector frenzy :-) François Pinard
2002-04-22 4:43 ` Karl Eichwalder
2002-04-22 5:29 ` David desJardins
2002-04-22 8:37 ` Pavel Janík
2002-04-22 7:23 ` Eli Zaretskii [this message]
2002-04-22 9:52 ` Andreas Schwab
2002-04-22 11:22 ` Eli Zaretskii
2002-04-22 14:31 ` Andreas Schwab
2002-04-22 9:38 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SUN.3.91.1020422101615.11473L-100000@is \
--to=eliz@is.elta.co.il \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).