On Tue, Mar 30, 1999 at 02:48:19PM -0600, Tim Walberg wrote:
> On 03/30/1999 13:06 -0500, Petr Hlustik wrote:
> >>
> >> I said in my original post that it did not dump core. I guess the exit
> >> status was zero, I ran this immediately after mutt quit:
> >>
> >> cortex:~>echo $?
> >> 0
> >> [7]+ Done rxvt +ls -n XMutt -bg black -fg white -tn
> >> rxvt -geometry 80x60 -fn -misc-*-bold-*-normal-*-14-80-*-*-*-*-*-2 -e mutt
>
> Of course, $? is not normally set as the exit code of a background
> process that exits (i.e. 'ls does_not_exist; echo $?' is not necessarily
> the same as 'ls does_not_exist & sleep 10; echo $?'), and even if it were,
> it would be the exit code from rxvt, not from mutt...
Thanks, I forgot about this second layer. Well, I recreated the situation,
now starting mutt directly from rxvt and now it dumps core after
segmentation fault. The exit code is 139. I am afraid that's the end of my
investigation; I am not a programmer... Anyway, this whole problem happened
because of my erroneus setting in the .muttrc file and was easily fixed.
Regards,
Petr
