From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: 29031@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#29031: 25.3; Segmentation fault when starting emacs with my config
Date: Tue, 07 Nov 2017 08:55:37 -0500 [thread overview]
Message-ID: <874lq65h2e.fsf@users.sourceforge.net> (raw)
In-Reply-To: <CAFyQvY0Di_9wLqijdsUziJrm3QF-1xcOq9u5usN1PxcOCGb4Tg@mail.gmail.com> (Kaushal Modi's message of "Tue, 07 Nov 2017 13:30:35 +0000")
Kaushal Modi <kaushal.modi@gmail.com> writes:
> I have no idea what that is. I am not a C developer. So I haven't yet
> found time to learn valgrind. I read the referenced DEBUG file, but
> it made no sense. I believe it's a steep learning curve for someone
> who doesn't know what valgrind is.
Could you try just installing valgrind, reconfiguring and recompile
emacs with --enable-checking (reconfigure after installing valgrind, as
configure checks for its header file) and then running 'valgrind emacs'
and posting the result. I tried this now without making any more
complex changes suggested in DEBUG and emacs did manage to run. There
were a couple of warnings about pselect and writev, but otherwise it
seemed to work okay.
It's possible something useful will come out. If not, we can consider
whether it's worth trying the more complex stuff.
next prev parent reply other threads:[~2017-11-07 13:55 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 [this message]
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
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
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=874lq65h2e.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=29031@debbugs.gnu.org \
--cc=kaushal.modi@gmail.com \
--cc=monnier@iro.umontreal.ca \
/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).