vim-enhanced oddness

[Ken Snider]

Nathan Bryant wrote:

> run it under the debugger gdb,
> 
> gdb vim
> run blah
> 
> after it crashes, capture a stack trace with the 'bt' command

To reproduce:

gdb vim
run blah
(enter some text, :wq out)

Result:

Program received signal SIGILL, Illegal instruction.
0x0000003f53301c30 in ?? () from /lib64/tls/libm.so.6
(gdb) bt
#0  0x0000003f53301c30 in ?? () from /lib64/tls/libm.so.6
#1  0x0000003f53702f28 in acl_get_file () from /lib64/libacl.so.1
#2  0x000000000044999a in ?? ()
#3  0x0000000000426010 in ?? ()
#4  0x0000000000437f13 in ?? ()
#5  0x0000000000433284 in ?? ()
#6  0x0000000000431a58 in ?? ()
#7  0x000000000048338e in ?? ()
#8  0x000000000047eb24 in ?? ()
#9  0x000000000045ac98 in ?? ()
#10 0x0000000000459ce9 in ?? ()
#11 0x0000003f5301d181 in __libc_start_main () from /lib64/tls/libc.so.6
#12 0x000000000040362a in ?? ()

I tried installing glibc-debug to see if I could get something more 
descriptive, but no luck.

-- 
Ken Snider