When I run the following macro mutt exits with segfault macro index S '<pipe-message>/home/axisys/.mutt/script/reportspam.sh<enter><delete-message>'
Here is the script #!/bin/bash # take the email and send it as attachment to abuse # save to tmp file spam=$(tempfile -s .eml) [email protected] cat > "$spam" # use formail to extract subject (could use grep in a pinch) subj=$(formail -x subject < $spam) if [ ! -z "$spam" ]; then mutt -e 'set [email protected]' -s "[spam]$subj" -a $spam -- "$ABUSE" fi rm "$spam" Here is the segfault in `dmesg' http://pastebin.com/29JuFUCv I am running mutt 1.5.20 on ubuntu lucid If I add `set -x' in that macro script this is how it reports about the segfault ++ tempfile -s .eml + spam=/tmp/fileMWDTFO.eml + [email protected] + cat - Segmentation fault ++ formail -x subject + subj= + '[' '!' -z /tmp/fileMWDTFO.eml ']' + mutt -e 'set [email protected]' -s '[spam]' -a /tmp/fileMWDTFO.eml -- [email protected] + rm /tmp/fileMWDTFO.eml Am I hitting a bug? Is there a way to run mutt in debug mode to get more details -- Asif Iqbal PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing?
