segfault

[Oliver Scholz]

I just got a segfault, this time on MS Windows (if that should
matter).

(gdb) bt
#0  0x011191ce in _free_internal (ptr=0x852a90) at gmalloc.c:1192
#1  0x011194e7 in _realloc_internal (ptr=0x852a90, size=12) at gmalloc.c:1395
#2  0x011195cd in e_realloc (ptr=0x852a90, size=12) at gmalloc.c:1488
#3  0x0102395b in emacs_blocked_realloc (ptr=0x852a90, size=12)
    at alloc.c:1038
#4  0x011195cd in e_realloc (ptr=0x852a90, size=12) at gmalloc.c:1488
#5  0x010232d8 in xrealloc (block=0x852a90, size=12) at alloc.c:547
#6  0x010e61a9 in coding_alloc_by_realloc (coding=0x82f430, bytes=8)
    at coding.c:935
#7  0x010e62c9 in alloc_destination (coding=0x82f430, nbytes=8,
    dst=0x852a90 "\r𭺫«««««««îþîþ") at coding.c:977
#8  0x010ef79b in encode_coding_charset (coding=0x82f430) at coding.c:4784
#9  0x010f17cb in encode_coding (coding=0x82f430) at coding.c:6141
#10 0x010f245a in encode_coding_object (coding=0x82f430,
    src_object=859965988, from=0, from_byte=0, to=2, to_byte=3,
    dst_object=291889156) at coding.c:6609
#11 0x0114731c in Fw32_set_clipboard_data (string=859965988, frame=291889156)
    at w32select.c:215
#12 0x0101f87e in Ffuncall (nargs=2, args=0x82f5d0) at eval.c:2727
#13 0x0110ccc3 in Fbyte_code (bytestr=824423708, vector=1092859196,
    maxdepth=2) at bytecode.c:710
#14 0x0101fc6d in funcall_lambda (fun=1092859112, nargs=2,
    arg_vector=0x82f6f4) at eval.c:2911
#15 0x0101f70e in Ffuncall (nargs=3, args=0x82f6f0) at eval.c:2781
---Type <return> to continue, or q <return> to quit---
#16 0x0110ccc3 in Fbyte_code (bytestr=823991916, vector=1092427488,
    maxdepth=7) at bytecode.c:710
#17 0x0101fc6d in funcall_lambda (fun=1092427312, nargs=1,
    arg_vector=0x82f824) at eval.c:2911
#18 0x0101f70e in Ffuncall (nargs=2, args=0x82f820) at eval.c:2781
#19 0x0110ccc3 in Fbyte_code (bytestr=823993348, vector=1092428856,
    maxdepth=4) at bytecode.c:710
#20 0x0101fc6d in funcall_lambda (fun=1092428756, nargs=2,
    arg_vector=0x82f944) at eval.c:2911
#21 0x0101f70e in Ffuncall (nargs=3, args=0x82f940) at eval.c:2781
#22 0x0110ccc3 in Fbyte_code (bytestr=823993640, vector=1092429252,
    maxdepth=6) at bytecode.c:710
#23 0x0101fc6d in funcall_lambda (fun=1092429048, nargs=2,
    arg_vector=0x82fab4) at eval.c:2911
#24 0x0101f70e in Ffuncall (nargs=3, args=0x82fab0) at eval.c:2781
#25 0x0110b4b1 in Fcall_interactively (function=300898124,
    record_flag=291889156, keys=1097247488) at callint.c:850
#26 0x0101239b in Fcommand_execute (cmd=300898124, record_flag=291889156,
    keys=291889156, special=291889156) at keyboard.c:9725
#27 0x01006e9e in command_loop_1 () at keyboard.c:1756
#28 0x0101d7b7 in internal_condition_case (bfun=0x1006b90 <command_loop_1>,
    handlers=292001276, hfun=0x1006620 <cmd_error>) at eval.c:1333
#29 0x0100694d in command_loop_2 () at keyboard.c:1292
#30 0x0101d2ff in internal_catch (tag=291957676,
---Type <return> to continue, or q <return> to quit---
    func=0x1006920 <command_loop_2>, arg=291889156) at eval.c:1094
#31 0x010068f7 in command_loop () at keyboard.c:1271
#32 0x010063d0 in recursive_edit_1 () at keyboard.c:987
#33 0x010064f9 in Frecursive_edit () at keyboard.c:1043
#34 0x01003158 in main (argc=3, argv=0xa22640) at emacs.c:1673


I need advice on how to track that bug down or at least how to
provide better information.

This is not the first time that I have a segfault with these
symptoms.  What should I do the next time? 

This bug is not easily reproducable. Is there a way in gdb to dump the
memory image of a process to a file and restore it later? So that I
can answer questions to you, if necessary, after I reported a segfault
at any later time?


    Oliver
-- 
Oliver Scholz               28 Brumaire an 212 de la Révolution
Taunusstr. 25               Liberté, Egalité, Fraternité!
60329 Frankfurt a. M.       http://www.jungdemokratenhessen.de
Tel. (069) 97 40 99 42      http://www.jdjl.org