From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 8334@debbugs.gnu.org
Subject: bug#8334: Segmentation fault in mark_object (in my patched version)
Date: Thu, 24 Mar 2011 10:42:03 -0400 [thread overview]
Message-ID: <jwvei5winuz.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878vw5nvcl.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 23 Mar 2011 21:46:50 -0400")
> The present bug is reported from a modified version of Emacs, but with
> no test case, no description of events leading to the crash, and an
> uninformative backtrace. For all we know, it is due to your own
> unspecified changes. So it is more profitable for Emacs developers to
> work on the bugs in our tree that need attention.
Actually, this is not the main reason, AFAIC. The problem is that we
simply have no way to debug it. Especially for a bug that causes
a segfault in the GC, i.e. a bug that apparently causes memory
corruption and could hence be anywhere.
Stefan
next prev parent reply other threads:[~2011-03-24 14:42 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-24 0:07 bug#8334: Segmentation fault in mark_object (in my patched version) Lennart Borgman
2011-03-24 0:49 ` Chong Yidong
2011-03-24 0:52 ` Lennart Borgman
2011-03-24 1:09 ` Chong Yidong
2011-03-24 1:20 ` Lennart Borgman
2011-03-24 1:46 ` Chong Yidong
2011-03-24 1:52 ` Lennart Borgman
2011-03-24 3:07 ` Juanma Barranquero
2011-03-24 9:24 ` Juanma Barranquero
2011-03-24 14:31 ` Lennart Borgman
2011-03-24 14:33 ` Lennart Borgman
2011-03-24 16:37 ` Chong Yidong
2011-03-24 14:42 ` Stefan Monnier [this message]
2011-03-24 14:48 ` Lennart Borgman
2012-03-27 22:42 ` Glenn Morris
[not found] ` <handler.8334.D8334.133289003225313.notifdone@debbugs.gnu.org>
2012-03-27 22:48 ` bug#8334: closed (Re: bug#8334: Segmentation fault in mark_object (in my patched version)) Lennart Borgman
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=jwvei5winuz.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=8334@debbugs.gnu.org \
--cc=cyd@stupidchicken.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.