Re: mutt - segmentation fault

[Johann Spies <jspies@sun.ac.za>]

On Wed, Oct 16, 2002 at 03:12:12PM +0200, Gottfried Szing wrote:
> 
> > Did anybody experience something similar?
> 
> i am also using the latest mutt and i have no problem. maybe you can try
> strace to identify the problem. try to run a 
> 
> $ strace -f -o mutt.log mutt 
> 
> and take a look at the last few lines where the segfault happens.

Thanks.  I also checked and saw that bug #97527 referred to something
similar.

My mutt.log ended with:

tail /tmp/mutt.log 
22657 fcntl64(4, F_SETFD, FD_CLOEXEC)   = 0
22657 fstat64(4, {st_mode=S_IFREG|0644, st_size=631, ...}) = 0
22657 old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40231000
22657 _llseek(4, 0, [0], SEEK_CUR)      = 0
22657 read(4, "root:x:0:\ndaemon:x:1:\nbin:x:2:\ns"..., 4096) = 631
22657 close(4)                          = 0
22657 munmap(0x40231000, 4096)          = 0
22657 time(NULL)                        = 1034871546
22657 --- SIGSEGV (Segmentation fault) ---
22657 +++ killed by SIGSEGV +++
zsh % 

BTW  I saw in the output of strace that mutt frequently reads
/etc/password and /etc/groups. Why would that be?

Regards.
Johann
-- 
Johann Spies          Telefoon: 021-808 4036
Informasietegnologie, Universiteit van Stellenbosch

     "Trust in the LORD, and do good..."        Psalms 37:3