bug#29031: 25.3; Segmentation fault when starting emacs with my config

[Eli Zaretskii]

> From: Kaushal Modi <kaushal.modi@gmail.com>
> Date: Mon, 30 Oct 2017 19:24:19 +0000
> Cc: 29031@debbugs.gnu.org, monnier@iro.umontreal.ca
> 
> Thread 1 "emacs" received signal SIGABRT, Aborted.
> 0x00000033e3032625 in raise () from /lib64/libc.so.6
> (gdb) bt
> #0  0x00000033e3032625 in raise () from /lib64/libc.so.6
> #1  0x00000033e3033e05 in abort () from /lib64/libc.so.6
> #2  0x00000033e3070537 in __libc_message () from /lib64/libc.so.6
> #3  0x00000033e3075f4e in malloc_printerr () from /lib64/libc.so.6
> #4  0x00000033e307a614 in _int_malloc () from /lib64/libc.so.6
> #5  0x00000033e307ab1c in malloc () from /lib64/libc.so.6
> #6  0x00000000005debb2 in lmalloc (size=8188) at alloc.c:1450
> #7  0x00000000005de7a5 in lisp_malloc (nbytes=8188, type=MEM_TYPE_NON_LISP) 
> at alloc.c:1088
> #8  0x00000000005df0f7 in allocate_string_data (s=0x21e8370, nchars=70, 
> nbytes=70) at alloc.c:2024
> #9  0x00000000005dfe78 in make_uninit_multibyte_string (nchars=70, nbytes=70) 
> at alloc.c:2548
> #10 0x00000000005dfd3e in make_specified_string (contents=0x7ffffffd6c50
> "SOME_FILE__JUST_MASKING_REAL_FILENAME_HERE.v", nchars=70, nbytes=70, 
> multibyte=false) at
> alloc.c:2508

Could be some bug in your glibc on that system?  Otherwise, how come
no one else sees such fundamental problems?

In any case, bugs in memory allocation need to find the code which
corrupted the data structures used by malloc, which happened somewhere
else in the code.  Maybe try running under valgrind (see the advice in
etc/DEBUG under "Running Emacs built with malloc debugging packages").