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

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

[debbugs-tracker] bug#17071: closed (24.3.50; emacs_backtrace.txt)


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#17071: closed (24.3.50; emacs_backtrace.txt)
Date: Tue, 12 Aug 2014 04:00:09 +0000

Your message dated Mon, 11 Aug 2014 23:59:53 -0400
with message-id <address@hidden>
and subject line Re: bug#17771: 24.3.91; SIGSEGV in cleanup_vector
has caused the debbugs.gnu.org bug report #17771,
regarding 24.3.50; emacs_backtrace.txt
to be marked as done.

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


-- 
17771: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17771
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3.50; emacs_backtrace.txt Date: Sun, 23 Mar 2014 09:21:59 -0700 (PDT)

Backtrace:
011ffa11
011ffa82
010f3fa7
01165fa5
01160734
0116081f
01165cf1
01163d60
010f20c7
01183f17
01181448
01029ed7
01029f14
01041a2f
01045cab
01047481
0100f120
01184193
011c4d84
01184975
011843cf
01182cfb
0117ea06
010f7b8a
01182b69
01182692
011841b9
011c4d84
01184975
011843cf
011c4d84
01184d39
011843cf
0117d977
011841e8
011c4d84
01184975
011843cf
01183c7e
010f8359
011810f3
010f79aa
011806a0
010f7962
010f70f8
010f72b4
010f54b8
010010f9
74df3366
77269f6e
77269f41




In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2014-03-10 on ODIEONE
Bzr revision: 116730 address@hidden
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
 'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib 'CPPFLAGS=-DGC_MCHECK=1
 -Ic:/Devel/emacs/include''



--- End Message ---
--- Begin Message --- Subject: Re: bug#17771: 24.3.91; SIGSEGV in cleanup_vector Date: Mon, 11 Aug 2014 23:59:53 -0400 User-agent: Gnus (www.gnus.org), GNU Emacs (www.gnu.org/software/emacs/)
Version: 24.3.93

Stephen Berman wrote:

> I see.  Well, having Emacs crash is certainly worse than not being able
> to interrupt fontconfig, so I think you should commit the patch, and
> then as far as I'm concerned, this bug can be closed.


--- End Message ---

reply via email to

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