On Fri, Aug 09, 2013 at 02:24:31PM +0100, James Griffin wrote: > I have the mutt.core dump file; can/should I send this to someone for > examination? [...] > I appreciate my fault report is mostly supposition. I have run gdb on the > core file, I can send the output if required. I haven't included it now > as I hoped someone could tell me what commands to run whilst in gdb to > get the most useful information.
It's probably most helpful if you can just send a backtrace. You can do that by running mutt in gdb with your core file, like this (use the path to your Mutt binary, instead of /usr/local/bin/mutt): $ gdb /usr/local/bin/mutt core GNU gdb (GDB) CentOS (7.0.1-45.el5.centos) [...] Program terminated with signal 11, Segmentation fault. #0 0xb77bc420 in __kernel_vsyscall () (gdb) bt #0 0xb77bc420 in __kernel_vsyscall () #1 0xb76a206d in ___newselect_nocancel () from /lib/libc.so.6 #2 0xb7798bf0 in _nc_timed_wait () from /usr/lib/libncursesw.so.5 #3 0xb777a49a in ?? () from /usr/lib/libncursesw.so.5 #4 0xb777b0e9 in _nc_wgetch () from /usr/lib/libncursesw.so.5 #5 0xb777b1dc in wgetch () from /usr/lib/libncursesw.so.5 #6 0x0805f4f0 in mutt_getch () at curs_lib.c:97 #7 0x0807a0e6 in km_dokey (menu=6) at keymap.c:448 #8 0x0806067c in mutt_index_menu () at curs_main.c:599 #9 0x0807c31d in main (argc=1, argv=0xbfc536e4) at main.c:1020 Note that I forced this core dump by sending mutt a SIGSEGV manually, this is not a bug. :) -- Derek D. Martin http://www.pizzashack.org/ GPG Key ID: 0xDFBEAD02 -=-=-=-=- This message is posted from an invalid address. Replying to it will result in undeliverable mail due to spam prevention. Sorry for the inconvenience.
pgpUb9Dy9dwCO.pgp
Description: PGP signature
