The stack is pretty short... Reading symbols from test/testdir/inst/usr/local/bin/dist...done. [New LWP 16558] Core was generated by `dist -noedit -to [email protected]'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000559ecc4d1816 in WhatNow (argc=1, argv=0x7ffebd4a6980) at uip/whatnowsbr.c:263 263 switch (smatch (*argp, aleqs)) { (gdb) bt #0 0x0000559ecc4d1816 in WhatNow (argc=1, argv=0x7ffebd4a6980) at uip/whatnowsbr.c:263 #1 0x0000559ecc4d1241 in what_now (ed=0x0, nedit=1, use=0, file=0x7ffebd4aa9d0 "/home/crichmon/Downloads/nmh/test/testdir/Mail/draft", altmsg=0x559ecde18100 "1", dist=1, mp=0x559ecde17590, text=0x0, inplace=1, cwd=0x559ecde17520 "/home/crichmon/Downloads/nmh", atfile=0) at uip/whatnowproc.c:122 #2 0x0000559ecc4d0cce in main (argc=4, argv=0x7ffebd4aeb78) at uip/dist.c:354
Thx, Chris -----Original Message----- From: Ken Hornstein <[email protected]> Sent: Thursday, November 7, 2019 4:13 PM To: Chris Richmond <[email protected]> Cc: [email protected] Subject: Re: 4 of 108 tests failed testing nmh >> gdb core >.... >Type "apropos word" to search for commands related to "word"... >"/home/crichmon/Downloads/nmh/core": not in executable format: File >format not recognized Ah, okay, we're very close. You need to run gdb on the executable AND the core file. Given the above information, it's probably something like: % gdb /home/crichmon/Downloads/nmh/test/testdir/inst/usr/local/bin/dist core Or if that complains about no symbols being loaded, maybe: % gdb uip/dist core At the gdb prompt you can get a backtrace with the "bt" command and that should show us the complete stack trace and where things are going wrong. --Ken
