GNU bug report logs - #25442
Emacs compilation buffer segfault

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 25442 in the body.
You can then email your comments to 25442 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: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: bug-guix <at> gnu.org
Subject: Emacs compilation buffer segfault
Date: Fri, 13 Jan 2017 22:21:16 +0100

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

Hi!

Running

    bash crash.nw
   
in an xterm makes Emacs segfault about 4 out of 5 times for me.

Greetings,
Jan

[crash.nw (application/octet-stream, attachment)]

[mes.crash (application/octet-stream, attachment)]

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

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  

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

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: 25442 <at> debbugs.gnu.org
Subject: stacktrace
Date: Sat, 14 Jan 2017 17:06:05 +0100

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

Find attached.  There is no debugging info, is there a package that
I can install which includes the debugging symbols?

[stacktrace (application/octet-stream, attachment)]

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

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  

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

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke <at> gnu.org>
Cc: 25442 <at> debbugs.gnu.org
Subject: Re: bug#25442: stacktrace
Date: Sat, 14 Jan 2017 18:24:18 +0100

Jan Nieuwenhuizen <janneke <at> gnu.org> skribis:

> Find attached.  There is no debugging info, is there a package that
> I can install which includes the debugging symbols?

The ‘emacs’ package currently doesn’t have a ‘debug’ output.  So you
would first need to add one:

  (outputs '("out" "debug"))

and then install both outputs:

  guix package -i emacs emacs:debug

See <https://www.gnu.org/software/guix/manual/html_node/Installing-Debugging-Files.html>.

HTH!

Ludo’.

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

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: 25442 <at> debbugs.gnu.org
Subject: Re: bug#25442: stacktrace
Date: Sat, 14 Jan 2017 20:56:15 +0100

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

Ludovic Courtès writes:

> The ‘emacs’ package currently doesn’t have a ‘debug’ output.  So you
> would first need to add one:
>
>   (outputs '("out" "debug"))
>
> and then install both outputs:
>
>   guix package -i emacs emacs:debug
>
> See
> <https://www.gnu.org/software/guix/manual/html_node/Installing-Debugging-Files.html>.

Thank you!  Very nice documentation.  As discussed on IRC it was needed
to not use grafts to avoid gdb `CRC mismatch'

    guix package --no-grafts -i emacs emacs:debug

I also set

    ~/.gdbinit
    set debug-file-directory ~/.guix-profile/lib/debug

and did

    guix build --source emacs
    tar xf /gnu/store/wqdh5lxyrkzjhxy2rvs7qsbrd07lw89i-emacs-25.1.tar.xz

and set

    (gdb) directory ~/src/guix/emacs-25.1/src

Now I have a full backtrace; attached.

I'm not sure how to continue here; I built Emacs from GIT and there the
problem is not present.  Looking at the diff from 25.1 until HEAD I do
not see any obvious patches, neither does the git log point me to one.

Greetings,
Jan

[bt (application/octet-stream, attachment)]

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

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  

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

From: ludo <at> gnu.org (Ludovic Courtès)
To: Jan Nieuwenhuizen <janneke <at> gnu.org>
Cc: 25442 <at> debbugs.gnu.org
Subject: Re: bug#25442: stacktrace
Date: Sun, 15 Jan 2017 21:30:00 +0100

Jan Nieuwenhuizen <janneke <at> gnu.org> skribis:

> Ludovic Courtès writes:
>
>> The ‘emacs’ package currently doesn’t have a ‘debug’ output.  So you
>> would first need to add one:
>>
>>   (outputs '("out" "debug"))
>>
>> and then install both outputs:
>>
>>   guix package -i emacs emacs:debug
>>
>> See
>> <https://www.gnu.org/software/guix/manual/html_node/Installing-Debugging-Files.html>.
>
> Thank you!  Very nice documentation.  As discussed on IRC it was needed
> to not use grafts to avoid gdb `CRC mismatch'
>
>     guix package --no-grafts -i emacs emacs:debug
>
> I also set
>
>     ~/.gdbinit
>     set debug-file-directory ~/.guix-profile/lib/debug
>
> and did
>
>     guix build --source emacs
>     tar xf /gnu/store/wqdh5lxyrkzjhxy2rvs7qsbrd07lw89i-emacs-25.1.tar.xz
>
> and set
>
>     (gdb) directory ~/src/guix/emacs-25.1/src
>
> Now I have a full backtrace; attached.

Cool, glad it worked.

> I'm not sure how to continue here; I built Emacs from GIT and there the
> problem is not present.  Looking at the diff from 25.1 until HEAD I do
> not see any obvious patches, neither does the git log point me to one.

So the question is whether this bug is introduced by our packaging or
whether it’s an upstream bug.

Perhaps you could build with (warning! this command does not
authenticate the tarball it downloads):

  guix package -i emacs emacs:debug \
    --with-source=ftp://alpha.gnu.org/gnu/emacs/emacs-25.1.91.tar.xz

or similarly with a nightly snapshot or Git checkout.

I’m afraid that’s all I can suggest now.

HTH!

Ludo’.

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

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: 25442 <at> debbugs.gnu.org
Subject: Re: bug#25442: stacktrace
Date: Sun, 15 Jan 2017 23:36:34 +0100

Ludovic Courtès writes:

>> I'm not sure how to continue here; I built Emacs from GIT and there the
>> problem is not present.  Looking at the diff from 25.1 until HEAD I do
>> not see any obvious patches, neither does the git log point me to one.
>
> So the question is whether this bug is introduced by our packaging or
> whether it’s an upstream bug.

Yes.

> Perhaps you could build with (warning! this command does not
> authenticate the tarball it downloads):
>
>   guix package -i emacs emacs:debug \
>     --with-source=ftp://alpha.gnu.org/gnu/emacs/emacs-25.1.91.tar.xz

   guix package -i emacs emacs:debug \
     --with-source=ftp://alpha.gnu.org/gnu/emacs/pretest/emacs-25.1.91.tar.xz

inserted /pretest here

> I’m afraid that’s all I can suggest now.

That's a good suggestion.  I have tried this and the bug is also gone
here, with our packaging.  So apparently it has been fixed upstream.

Thanks!
Greetings,
Jan

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl  

Message #25 received at 25442-done <at> debbugs.gnu.org (full text, mbox):

From: Jan Nieuwenhuizen <janneke <at> gnu.org>
To: ludo <at> gnu.org (Ludovic Courtès)
Cc: 25442-done <at> debbugs.gnu.org
Subject: Re: bug#25442: stacktrace
Date: Sat, 30 Sep 2017 09:36:26 +0200

Jan Nieuwenhuizen writes:

> That's a good suggestion.  I have tried this and the bug is also gone
> here, with our packaging.  So apparently it has been fixed upstream.

long fixed, long -done.
janneke

-- 
Jan Nieuwenhuizen <janneke <at> gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Previous Next

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