emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#25442: closed (Emacs compilation buffer segfault)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#25442: closed (Emacs compilation buffer segfault)
Date: Sat, 30 Sep 2017 07:37:02 +0000

Your message dated Sat, 30 Sep 2017 09:36:26 +0200
with message-id <address@hidden>
and subject line Re: bug#25442: stacktrace
has caused the debbugs.gnu.org bug report #25442,
regarding Emacs compilation buffer segfault
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
25442: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=25442
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: Emacs compilation buffer segfault Date: Fri, 13 Jan 2017 22:21:16 +0100
Hi!

Running

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

Greetings,
Jan

Attachment: crash.nw
Description: Binary data

Attachment: mes.crash
Description: Binary data

-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ®  http://AvatarAcademy.nl  

--- End Message ---
--- Begin Message --- Subject: Re: bug#25442: stacktrace Date: Sat, 30 Sep 2017 09:36:26 +0200 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (gnu/linux)
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 <address@hidden> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | AvatarĀ® http://AvatarAcademy.com


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]