GNU bug report logs - #23572
Emacs segfaults at start since commit '374f6a5f3...'

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 23572 in the body.
You can then email your comments to 23572 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Vladimir Lomov <lomov.vl <at> gmail.com>
To: bug-gnu-emacs <at> gnu.org
Subject: Emacs segfaults at start since commit '374f6a5f3...'
Date: Wed, 18 May 2016 22:31:23 +0800

[Message part 1 (text/plain, inline)]

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.

---
Vladimir Lomov

-- 
Get Revenge!  Live long enough to be a problem for your children!

[valgrind.log (text/plain, attachment)]

[gdb.txt (text/plain, attachment)]

Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Rasmus <rasmus <at> gmx.us>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#23572: Emacs segfaults at start since commit '374f6a5f3...'
Date: Wed, 18 May 2016 17:01:33 +0200

Vladimir Lomov <lomov.vl <at> 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.

Thanks,
Rasmus

-- 
Don't panic!!!

Message #11 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Zack Piper <zack <at> apertron.net>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#23572: Emacs segfaults at start since commit '374f6a5f3...'
Date: Wed, 18 May 2016 15:46:28 +0000

On Wed, May 18, 2016 at 05:01:33PM +0200, Rasmus wrote:
> Vladimir Lomov <lomov.vl <at> 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.

Also getting the same crash, tried sending a bug report earlier, but my SMTPd died. :(

-- 
Zack Piper <zack <at> apertron.net> https://apertron.net

Message #14 received at 23572 <at> debbugs.gnu.org (full text, mbox):

From: Alan Mackenzie <acm <at> muc.de>
To: 23572 <at> debbugs.gnu.org
Cc: Rasmus <rasmus <at> gmx.us>
Subject: Re: bug#23572: Emacs segfaults at start since commit '374f6a5f3...'
Date: 18 May 2016 18:14:08 -0000

In article <mailman.71.1463583733.6543.bug-gnu-emacs <at> gnu.org> you wrote:
> Vladimir Lomov <lomov.vl <at> 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).

Message #17 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Zack Piper <zack <at> apertron.net>
To: bug-gnu-emacs <at> gnu.org
Subject: Re: bug#23572: Emacs segfaults at start since commit '374f6a5f3...'
Date: Wed, 18 May 2016 18:32:46 +0000

On Wed, May 18, 2016 at 06:14:08PM -0000, Alan Mackenzie wrote:
> In article <mailman.71.1463583733.6543.bug-gnu-emacs <at> gnu.org> you wrote:
> > Vladimir Lomov <lomov.vl <at> 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)

"07ebcf1bd..." is 07ebcf1bd964ae64446c52fb5481e919ed577358:

commit 07ebcf1bd964ae64446c52fb5481e919ed577358
Refs: [HEAD], emacs-24.5-rc3-fixed-9323-g07ebcf1
Author:     Paul Eggert <eggert <at> cs.ucla.edu>
AuthorDate: Wed May 18 00:48:35 2016 -0700
Commit:     Paul Eggert <eggert <at> cs.ucla.edu>
CommitDate: Wed May 18 00:49:30 2016 -0700

    ‘make check-declare’ now chatters less

    * etc/NEWS: Document this.
    * lisp/emacs-lisp/check-declare.el (check-declare-locate):
    Return relative names, not absolute.
    (check-declare-scan, check-declare-verify, check-declare-warn)
    (check-declare-file, check-declare-directory):
    Generate less chatter.  Use relative file names rather than
    absolute.  Don’t give up on computing a good file name for a
    diagnostic merely because the function name was bad.  Make
    malformed declarations more noticeable.  Don’t warn about
    "ext:..." declarations if check-declare-ext-errors is nil.
    (check-declare-errmsg): Remove.
    (check-declare-warn): New optional arg LINE.
    (check-declare-files): Put status into mode line rather than
    chattering.

"6f5db0255..." is 6f5db0255cab2e17ab53ee68f6dc2f4d75978d80:

commit 6f5db0255cab2e17ab53ee68f6dc2f4d75978d80
Refs: [HEAD], emacs-24.5-rc3-fixed-9318-g6f5db02
Author:     Paul Eggert <eggert <at> cs.ucla.edu>
AuthorDate: Wed May 18 00:05:53 2016 -0700
Commit:     Paul Eggert <eggert <at> cs.ucla.edu>
CommitDate: Wed May 18 00:49:28 2016 -0700

    Sync from gnulib

    This incorporates:
    2016-05-17 manywarnings: update for GCC 6.1
    2016-05-13 intdiv0, memmem, nocrash, strcasestr, strstr: no exit
    * m4/manywarnings.m4, m4/nocrash.m4: Copy from gnulib.

"374f6a5f3..." is 374f6a5f34a83d3e4c518f0726558642293fdd71:

commit 374f6a5f34a83d3e4c518f0726558642293fdd71
Refs: [HEAD]
Author:     Paul Eggert <eggert <at> cs.ucla.edu>
AuthorDate: Wed May 18 00:06:12 2016 -0700
Commit:     Paul Eggert <eggert <at> cs.ucla.edu>
CommitDate: Wed May 18 00:49:29 2016 -0700

    Port --enable-gcc-warnings to GCC 6.1

Hope this helps!


-- 
Zack Piper <zack <at> apertron.net> https://apertron.net

Message #20 received at 23572 <at> debbugs.gnu.org (full text, mbox):

From: Alan Mackenzie <acm <at> muc.de>
To: 23572 <at> debbugs.gnu.org
Cc: Zack Piper <zack <at> apertron.net>
Subject: Re: bug#23572: Emacs segfaults at start since commit '374f6a5f3...'
Date: 19 May 2016 07:34:24 -0000

In article <mailman.98.1463596448.6543.bug-gnu-emacs <at> 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 <at> gnu.org> you wrote:
>> > Vladimir Lomov <lomov.vl <at> 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 <at> cs.ucla.edu>
> AuthorDate: Wed May 18 00:48:35 2016 -0700
> Commit:     Paul Eggert <eggert <at> cs.ucla.edu>
> CommitDate: Wed May 18 00:49:30 2016 -0700

>     ‘make check-declare’ now chatters less

[ .... ]

> -- 
> Zack Piper <zack <at> apertron.net> https://apertron.net

-- 
Alan Mackenzie (Nuremberg, Germany).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.