From: Richard Stallman <rms@gnu.org>
To: "Kalman Reti" <kalman.reti@gmail.com>
Cc: bug-gnu-emacs@gnu.org, kalman.reti@gmail.com, emacs-devel@gnu.org
Subject: Re: mark_object crash in 22.1 and latest CVS (as of tonight)
Date: Tue, 13 Nov 2007 00:10:01 -0500 [thread overview]
Message-ID: <E1Iro2D-0000Hx-AO@fencepost.gnu.org> (raw)
In-Reply-To: <16af2f430711120340q27926877tf976ef397d12df16@mail.gmail.com> (kalman.reti@gmail.com)
I assumed
someone would recognize WHAT part of a buffer from the contents of the,
list, a mixture of conses with marker-in-no-buffer in the car of some and
Lisp_Misc_Free in the car of others, the cdr's being negative numbers
of pretty small absolute magnitude.
I didn't see that when I looked at the other message. Can anyone
guess what data this is?
> Once you answer those, you can try to figure out how it happened
> that the data structure ended up with a bad pointer.
> Maybe GC failed to mark that pointer, so the misc object got freed
> even though it was still in use.
Are there any tools to help with this, e.g. an allocation trace or GC trace?
I'm afraid this is the first time I've looked at the Emacs src code.
The x... GDB commands in .gdbinit are useful for examining data
structures during GC.
`last_marked' and `last_marked_index' keep track of the sequence of
data objects that were marked. You can use that to determine precisely
how the bad data was reached.
prev parent reply other threads:[~2007-11-13 5:10 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 3:55 mark_object crash in 22.1 and latest CVS (as of tonight) Kalman Reti
2007-11-09 11:32 ` Kalman Reti
2007-11-10 10:19 ` Kalman Reti
2007-11-11 5:22 ` Richard Stallman
2007-11-12 11:40 ` Kalman Reti
2007-11-12 22:03 ` Stefan Monnier
2007-11-13 0:30 ` Kalman Reti
2007-11-13 20:03 ` Richard Stallman
2007-11-14 17:39 ` Kalman Reti
2007-11-14 18:51 ` Stefan Monnier
2007-11-15 1:00 ` Kalman Reti
2007-11-15 17:09 ` Richard Stallman
2007-11-16 12:05 ` Kalman Reti
2007-11-16 14:07 ` Kalman Reti
2007-11-16 17:28 ` martin rudalics
2007-11-16 17:56 ` Kalman Reti
2007-11-17 4:54 ` Richard Stallman
2007-11-17 5:43 ` Kalman Reti
2007-11-16 19:04 ` Stefan Monnier
2007-11-16 21:52 ` martin rudalics
2007-11-16 22:09 ` Stefan Monnier
2007-11-16 22:16 ` Stefan Monnier
2007-11-16 23:59 ` Kalman Reti
2007-11-17 4:25 ` Stefan Monnier
2007-11-17 17:42 ` Richard Stallman
2007-11-18 3:08 ` Stefan Monnier
2007-11-18 22:45 ` Richard Stallman
2007-11-18 23:22 ` David Kastrup
2007-11-19 7:50 ` Stefan Monnier
2007-11-19 19:03 ` Richard Stallman
2007-11-17 4:53 ` Richard Stallman
2007-11-15 3:08 ` Richard Stallman
2007-11-15 8:38 ` Kalman Reti
2007-11-16 20:48 ` Kalman Reti
2007-11-16 21:59 ` Stefan Monnier
2007-11-16 23:09 ` martin rudalics
2008-02-04 11:35 ` buffer-undo-list (was: mark_object crash in 22.1 and latest CVS (as of tonight)) Johan Bockgård
2008-02-04 21:44 ` buffer-undo-list Stefan Monnier
2008-02-11 17:58 ` buffer-undo-list Stefan Monnier
2007-11-13 5:10 ` Richard Stallman [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1Iro2D-0000Hx-AO@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=bug-gnu-emacs@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kalman.reti@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.