Subject: bug#25442: closed (Re: bug#25442: stacktrace)

From: [email-masked] (GNU bug Tracking System)
Date: Sat, 30 Sep 2017 07:37:02 +0000

Your bug report

#25442: Emacs compilation buffer segfault

which was filed against the guix package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
25442: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25442
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#25442: stacktrace
From: Jan Nieuwenhuizen <[email-masked]>
To: [email-masked] (Ludovic Courtès)
Cc: [email-masked]
Date: Sat, 30 Sep 2017 09:36:26 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

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 <[email-masked]> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com

Subject: Emacs compilation buffer segfault
From: Jan Nieuwenhuizen <[email-masked]>
To: [email-masked]
Date: Fri, 13 Jan 2017 22:21:16 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

Hi!

Running

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

Greetings,
Jan

-- 
Jan Nieuwenhuizen <[email-masked]> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar®  http://AvatarAcademy.nl