From: "Jorgen Schäfer" <jorgen.schaefer@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21666@debbugs.gnu.org
Subject: bug#21666: Bug is indeed undo-list and GC related
Date: Wed, 09 Mar 2016 15:21:45 +0000 [thread overview]
Message-ID: <CALqDrSdEQZbhd8T+aJGZxoNJML+mMF=vjjLvCjQ0z-QMyREHrQ@mail.gmail.com> (raw)
In-Reply-To: <83mvq7ptrj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 774 bytes --]
No, I can not. As mentioned, the problem occurs after a day or two of
usage. If you understand the problem better now that you know what prevents
it, I am of course happy to run test cases.
Eli Zaretskii <eliz@gnu.org> schrieb am Mi., 9. März 2016 16:15:
> > From: Jorgen Schäfer <jorgen.schaefer@gmail.com>
> > Date: Wed, 09 Mar 2016 10:14:35 +0000
> >
> > I do not know how GC works in Emacs Lisp, but it seems to me that an
> Emacs Lisp program should not be
> > able to segfault Emacs in this manner. It is interesting that this
> problem was introduced sometime after
> > 19efb9 – an Emacs built from that commit did not exhibit the problem.
>
> Can you bisect it more narrowly? "After 19efb9" leaves a lot of
> alternatives...
>
> Thanks.
>
[-- Attachment #2: Type: text/html, Size: 1113 bytes --]
next prev parent reply other threads:[~2016-03-09 15:21 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-11 6:50 bug#21666: 25.0.50; Random segfaults Jorgen Schaefer
2015-10-12 0:30 ` Paul Eggert
2015-10-13 11:50 ` Jorgen Schaefer
2015-10-13 16:09 ` Paul Eggert
2015-10-15 11:05 ` Jorgen Schäfer
2015-10-16 8:03 ` Jorgen Schäfer
2015-10-16 8:05 ` Paul Eggert
2015-10-16 9:03 ` Eli Zaretskii
2015-10-16 22:28 ` Paul Eggert
2015-10-17 8:06 ` Eli Zaretskii
2015-10-23 9:41 ` Jorgen Schäfer
2015-10-23 10:04 ` Eli Zaretskii
2015-10-23 10:26 ` Eli Zaretskii
[not found] ` <handler.21666.B.144458332816487.ack@debbugs.gnu.org>
2015-11-29 19:13 ` bug#21666: Acknowledgement (25.0.50; Random segfaults) Jorgen Schäfer
2016-03-09 10:14 ` bug#21666: Bug is indeed undo-list and GC related Jorgen Schäfer
2016-03-09 15:15 ` Eli Zaretskii
2016-03-09 15:21 ` Jorgen Schäfer [this message]
2016-03-09 15:43 ` Phillip Lord
2016-03-09 16:37 ` Eli Zaretskii
2016-03-09 16:46 ` Jorgen Schäfer
2016-03-12 14:43 ` Jorgen Schäfer
2016-03-12 16:22 ` Eli Zaretskii
2016-03-12 23:44 ` Phillip Lord
2016-03-13 9:26 ` martin rudalics
2016-03-13 19:58 ` Phillip Lord
2016-03-13 20:12 ` martin rudalics
2016-03-14 19:56 ` bug#21666: Correction, emacs-25 *is* broken Jorgen Schäfer
2016-03-14 20:09 ` Eli Zaretskii
2016-03-14 20:21 ` Jorgen Schäfer
2016-03-14 20:53 ` Eli Zaretskii
2016-03-14 20:28 ` Phillip Lord
2016-03-14 20:41 ` Jorgen Schäfer
2018-06-12 23:01 ` bug#21666: 25.0.50; Random segfaults Noam Postavsky
2018-06-13 7:52 ` Jorgen Schäfer
2018-06-13 10:31 ` Noam Postavsky
2016-03-14 21:20 ` bug#21666: Backtrace Jorgen Schäfer
2016-03-14 22:19 ` Jorgen Schäfer
2016-03-15 3:36 ` Eli Zaretskii
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='CALqDrSdEQZbhd8T+aJGZxoNJML+mMF=vjjLvCjQ0z-QMyREHrQ@mail.gmail.com' \
--to=jorgen.schaefer@gmail.com \
--cc=21666@debbugs.gnu.org \
--cc=eliz@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).