bug#16473: 24.3.50; emacs_backtrace.txt

bug#16473: 24.3.50; emacs_backtrace.txt

[Drew Adams]

This looks similar to #16414, at least the beginning.

Backtrace:
011fb370
011fb3e1
010efc86
01161b55
010eba10
010ec480
010b29e8
011369f4
01136da7
01136a43
0113860d
0117cc49
01138b15
010f18b5
010efc3e
01161b55
0115ae52
0115ad24
01161056
0115f910
010ede0f
011c091a
01180909
0117ff9f
011c080c
01180909
0117ff9f
011c080c
01180909
0117ff9f
0117f307
0117f70e
0117f37e
0117fc53
011c080c
01180545
0117ff9f
0117e8cb
0117cb3e
011c174c
01180545
0117ff9f
011c080c
01180545
0117ff9f
0117cf9e
01026c50
01026c8d
01029eeb
010290ce
0103565e
01032228
01058fe4
0104dd83
0104b37b
01044652
0117cd5c
010445df
01043615
01041692
010f6238
011036c9
...




In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
 of 2014-01-07 on ODIEONE
Bzr revision: 115916 bzg@gnu.org-20140107233629-du2solx6tmxnx0np
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=-Ic:/Devel/emacs/include'

bug#16473: 24.3.50; emacs_backtrace.txt

[Drew Adams]

What's more, I was editing a file (call it `foo.el') when Emacs crashed. And in the next Emacs session I see an automatically created file named `.#foo.el'.  That file contains only this text, where USER is my user name and MACHINE is my machine name:

USER@MACHINE.1700:1389829856

Worse, the file I was editing has disappeared altogether - no autosave file.

I have never noticed this happen before.  Fortunately, the file I was editing was not very important.  I don't recall whether I had actually saved it prior to the crash.

bug#16473: 24.3.50; emacs_backtrace.txt

[Eli Zaretskii]

> Date: Thu, 16 Jan 2014 19:37:29 -0800 (PST)
> From: Drew Adams <drew.adams@oracle.com>
> 
> What's more, I was editing a file (call it `foo.el') when Emacs crashed. And in the next Emacs session I see an automatically created file named `.#foo.el'.  That file contains only this text, where USER is my user name and MACHINE is my machine name:
> 
> USER@MACHINE.1700:1389829856

This is the "user lock" file, created by Emacs to prevent accidental
editing of the same file from more than one Emacs session.  (The
second session will warn you about the lock; see the node
"Interlocking" in the user manual for more details.)  The fact that
this file is created whenever you have unsaved changes is normal.

> Worse, the file I was editing has disappeared altogether - no autosave file.

This is not good, but can happen (hopefully, rarely).

bug#16473: 24.3.50; emacs_backtrace.txt

[Juanma Barranquero]

??
??:0
w32_backtrace at w32fns.c:8386
emacs_abort at w32fns.c:8418
terminate_due_to_signal at emacs.c:378
die at alloc.c:6761
XVECTOR at lisp.h:827
AREF at lisp.h:1314
coding_inherit_eol_type at coding.c:6030
Fchoose_write_coding_system at fileio.c:4637
write_region at fileio.c:4807
Fwrite_region at fileio.c:4681
auto_save_1 at fileio.c:5469
internal_condition_case at eval.c:1345
Fdo_auto_save at fileio.c:5679
shut_down_emacs at emacs.c:2017
terminate_due_to_signal at emacs.c:362
die at alloc.c:6761
compact_small_strings at alloc.c:1960
sweep_strings at alloc.c:1890
gc_sweep at alloc.c:6333
Fgarbage_collect at alloc.c:5572
maybe_gc at lisp.h:4518
exec_byte_code at bytecode.c:954
funcall_lambda at eval.c:3040
Ffuncall at eval.c:2855
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3040
Ffuncall at eval.c:2855
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:3040
Ffuncall at eval.c:2855
funcall_nil at eval.c:2357
run_hook_with_args at eval.c:2542
Frun_hook_with_args at eval.c:2403
Ffuncall at eval.c:2787
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2974
Ffuncall at eval.c:2855
eval_sub at eval.c:2148
internal_lisp_condition_case at eval.c:1314
exec_byte_code at bytecode.c:1169
funcall_lambda at eval.c:2974
Ffuncall at eval.c:2855
exec_byte_code at bytecode.c:919
funcall_lambda at eval.c:2974
Ffuncall at eval.c:2855
internal_condition_case_n at eval.c:1427
safe_call at xdisp.c:2563
safe_call1 at xdisp.c:2579
handle_fontified_prop at xdisp.c:3755
handle_stop at xdisp.c:3319
next_element_from_buffer at xdisp.c:8075
get_next_display_element at xdisp.c:6730
display_line at xdisp.c:19710
try_window at xdisp.c:16541
redisplay_window at xdisp.c:16058
redisplay_window_0 at xdisp.c:14054
internal_condition_case_1 at eval.c:1369
redisplay_windows at xdisp.c:14034
redisplay_internal at xdisp.c:13633
redisplay at xdisp.c:12919
read_char at keyboard.c:2563
read_key_sequence at keyboard.c:9071
??
??:0

bug#16473: 24.3.50; emacs_backtrace.txt

[Eli Zaretskii]

> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 19 Jan 2014 23:20:04 +0100
> Cc: 16473@debbugs.gnu.org
> 
> w32_backtrace at w32fns.c:8386
> emacs_abort at w32fns.c:8418
> terminate_due_to_signal at emacs.c:378
> die at alloc.c:6761
> XVECTOR at lisp.h:827
> AREF at lisp.h:1314
> coding_inherit_eol_type at coding.c:6030
> Fchoose_write_coding_system at fileio.c:4637
> write_region at fileio.c:4807
> Fwrite_region at fileio.c:4681
> auto_save_1 at fileio.c:5469
> internal_condition_case at eval.c:1345
> Fdo_auto_save at fileio.c:5679
> shut_down_emacs at emacs.c:2017
> terminate_due_to_signal at emacs.c:362
> die at alloc.c:6761
> compact_small_strings at alloc.c:1960
> sweep_strings at alloc.c:1890
> gc_sweep at alloc.c:6333
> Fgarbage_collect at alloc.c:5572

An abort during GC here:

          nbytes = s ? STRING_BYTES (s) : SDATA_NBYTES (from);
          eassert (nbytes <= LARGE_STRING_BYTES);  <<<<<<<<<<<<<<<

followed by another abort during emergency shutdown.

bug#16473: 24.3.50; emacs_backtrace.txt

[Lars Ingebrigtsen]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Juanma Barranquero <lekktu@gmail.com>
>> Date: Sun, 19 Jan 2014 23:20:04 +0100
>> Cc: 16473@debbugs.gnu.org
>> 
>> w32_backtrace at w32fns.c:8386
>> emacs_abort at w32fns.c:8418
>> terminate_due_to_signal at emacs.c:378
>> die at alloc.c:6761
>> XVECTOR at lisp.h:827
>> AREF at lisp.h:1314
>> coding_inherit_eol_type at coding.c:6030
>> Fchoose_write_coding_system at fileio.c:4637
>> write_region at fileio.c:4807
>> Fwrite_region at fileio.c:4681
>> auto_save_1 at fileio.c:5469
>> internal_condition_case at eval.c:1345
>> Fdo_auto_save at fileio.c:5679
>> shut_down_emacs at emacs.c:2017
>> terminate_due_to_signal at emacs.c:362
>> die at alloc.c:6761
>> compact_small_strings at alloc.c:1960
>> sweep_strings at alloc.c:1890
>> gc_sweep at alloc.c:6333
>> Fgarbage_collect at alloc.c:5572
>
> An abort during GC here:
>
>           nbytes = s ? STRING_BYTES (s) : SDATA_NBYTES (from);
>           eassert (nbytes <= LARGE_STRING_BYTES);  <<<<<<<<<<<<<<<
>
> followed by another abort during emergency shutdown.

Is there anything more to be done here?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

bug#16473: 24.3.50; emacs_backtrace.txt

[Eli Zaretskii]

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: Juanma Barranquero <lekktu@gmail.com>,  16473@debbugs.gnu.org,  drew.adams@oracle.com
> Date: Sat, 26 Dec 2015 13:54:09 +0100
> 
> > An abort during GC here:
> >
> >           nbytes = s ? STRING_BYTES (s) : SDATA_NBYTES (from);
> >           eassert (nbytes <= LARGE_STRING_BYTES);  <<<<<<<<<<<<<<<
> >
> > followed by another abort during emergency shutdown.
> 
> Is there anything more to be done here?

No, I don't think so.