From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: 29031@debbugs.gnu.org, stefan@marxist.se,
monnier@iro.umontreal.ca, kaushal.modi@gmail.com
Subject: bug#29031: 25.3; Segmentation fault when starting emacs with my config
Date: Sun, 29 Sep 2019 10:26:39 +0300 [thread overview]
Message-ID: <83wodrftqo.fsf@gnu.org> (raw)
In-Reply-To: <87impb9ava.fsf@gmail.com> (message from Noam Postavsky on Sat, 28 Sep 2019 20:58:33 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Cc: 29031@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>, Kaushal Modi <kaushal.modi@gmail.com>
> Date: Sat, 28 Sep 2019 20:58:33 -0400
>
> It would likely be more productive to do this on a version from master,
> since I believe the switch to pdumper solves some potential problems
> when using valgrind.
I agree. I expect this problem not to happen at all in Emacs 27.
next prev parent reply other threads:[~2019-09-29 7:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 21:24 bug#29031: 25.3; Segmentation fault when starting emacs with my config Kaushal Modi
2017-10-30 14:17 ` Kaushal Modi
2017-10-30 16:03 ` Kaushal Modi
2017-10-30 18:37 ` Eli Zaretskii
2017-10-30 19:24 ` Kaushal Modi
2017-10-30 19:34 ` Eli Zaretskii
2017-10-30 19:51 ` Eli Zaretskii
2017-10-30 21:36 ` Kaushal Modi
2017-10-31 20:26 ` Eli Zaretskii
2017-10-31 20:52 ` Kaushal Modi
2017-10-31 20:56 ` Eli Zaretskii
2017-11-07 13:27 ` Noam Postavsky
2017-11-07 13:30 ` Kaushal Modi
2017-11-07 13:55 ` Noam Postavsky
2017-10-30 18:22 ` Eli Zaretskii
2017-10-30 18:34 ` Kaushal Modi
2017-10-30 18:52 ` Eli Zaretskii
2017-10-30 18:57 ` Kaushal Modi
2017-10-30 19:18 ` Kaushal Modi
2017-10-30 19:28 ` Eli Zaretskii
2019-09-29 0:44 ` Stefan Kangas
2019-09-29 0:58 ` Noam Postavsky
2019-09-29 7:26 ` Eli Zaretskii [this message]
2019-10-30 20:17 ` Stefan Kangas
2019-10-30 20:47 ` Kaushal Modi
2019-10-30 21:16 ` Stefan Kangas
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=83wodrftqo.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=29031@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=npostavs@gmail.com \
--cc=stefan@marxist.se \
/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.