From: Alan Mackenzie <acm@muc.de>
To: 23572@debbugs.gnu.org
Cc: Zack Piper <zack@apertron.net>
Subject: bug#23572: Emacs segfaults at start since commit '374f6a5f3...'
Date: 19 May 2016 07:34:24 -0000 [thread overview]
Message-ID: <20160519073424.1630.qmail@mail.muc.de> (raw)
In-Reply-To: <mailman.98.1463596448.6543.bug-gnu-emacs@gnu.org>
In article <mailman.98.1463596448.6543.bug-gnu-emacs@gnu.org> you wrote:
> On Wed, May 18, 2016 at 06:14:08PM -0000, Alan Mackenzie wrote:
>> In article <mailman.71.1463583733.6543.bug-gnu-emacs@gnu.org> you wrote:
>> > Vladimir Lomov <lomov.vl@gmail.com> writes:
>>
>> >> Hello,
>> >>
>> >> I faced with emacs segfault on start. I compiled emacs from git commit
>> >> '07ebcf1bd...' on my system: Archlinux x86_64, gcc 6.1.1 and run it in
>> >> terminal and it segfaulted, see attached output from GDB and valgrind.
>> >> While emacs compiled from git commit '6f5db0255...' works fine, so I
>> >> suspect that commit '374f6a5f3...' has introduced some bug or was
>> >> incompleted.
>>
>> > For what it is worth, I see the same crash, but I suspect my setup is very
>> > similar to Vladimir’s.
>>
>> I'm afraid I'm one of these strange people who don't have a memory for
>> the heads of 40-digit hex hashes.
>>
>> Do you think one of you might decipher these hashes for people like me?
>> Something like a date and the first line of the commit message would be
>> ideal.
>>
>> Thanks!
>>
>> > Thanks,
>> > Rasmus
>>
>> > --
>> > Don't panic!!!
>>
>> --
>> Alan Mackenzie (Nuremberg, Germany).
>>
>>
>>
>>
> (FYI Git can work with these fine, `git checkout 07ebcf1bd` goes to the commit mentioned)
Yes, I'm aware of this. The point I was trying to make is that the OP,
and also the follow-up posters, were subjecting the entire community to
the unnecessary work of looking up these hash codes. This makes me
annoyed. I was gently suggesting that people not repeat this practise.
Anyhow, thanks for posting the information. There is nothing in any of
these commits I know anything about.
> "07ebcf1bd..." is 07ebcf1bd964ae64446c52fb5481e919ed577358:
> commit 07ebcf1bd964ae64446c52fb5481e919ed577358
> Refs: [HEAD], emacs-24.5-rc3-fixed-9323-g07ebcf1
> Author: Paul Eggert <eggert@cs.ucla.edu>
> AuthorDate: Wed May 18 00:48:35 2016 -0700
> Commit: Paul Eggert <eggert@cs.ucla.edu>
> CommitDate: Wed May 18 00:49:30 2016 -0700
> ‘make check-declare’ now chatters less
[ .... ]
> --
> Zack Piper <zack@apertron.net> https://apertron.net
--
Alan Mackenzie (Nuremberg, Germany).
prev parent reply other threads:[~2016-05-19 7:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 14:31 bug#23572: Emacs segfaults at start since commit '374f6a5f3...' Vladimir Lomov
2016-05-18 15:01 ` Rasmus
2016-05-18 15:46 ` Zack Piper
[not found] ` <mailman.71.1463583733.6543.bug-gnu-emacs@gnu.org>
2016-05-18 18:14 ` Alan Mackenzie
2016-05-18 18:32 ` Zack Piper
[not found] ` <mailman.98.1463596448.6543.bug-gnu-emacs@gnu.org>
2016-05-19 7:34 ` Alan Mackenzie [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=20160519073424.1630.qmail@mail.muc.de \
--to=acm@muc.de \
--cc=23572@debbugs.gnu.org \
--cc=zack@apertron.net \
/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.