Re: seg fault

[Ken Weingold <bofh@xxxxxxx>]

On Thu, Aug 18, 2005, Nathan Dushman wrote:
> That's almost helpful, but not quite.  Could you compile mutt with debugging 
> enabled, and then run mutt again in gdb?  When it crashes, run "backtrace" 
> and send that output to the mutt-dev list.

I think I've mentioned it, but this is with NetBSD 2.0.

Here's the backtrace:

#0  0x4816a860 in fseek () from /usr/lib/libc.so.12
#1  0x4816a73c in rewind () from /usr/lib/libc.so.12
#2  0x0809de5f in pgp_application_pgp_handler (m=0x80f7800, s=0xbfbfe590)
    at pgp.c:384
#3  0x08052d44 in crypt_pgp_application_pgp_handler (m=0x80f7800, s=0xbfbfe590)
    at cryptglue.c:153
#4  0x0806bf05 in mutt_body_handler (b=0x80f7800, s=0xbfbfe590)
    at handler.c:1935
#5  0x080592bc in _mutt_copy_message (fpout=0x4819a298, fpin=0x4819a240, 
    hdr=0x80f7700, body=0x80f7800, flags=2124, chflags=150) at copy.c:661
#6  0x08059791 in mutt_copy_message (fpout=0x4819a298, src=0x8120c80, 
    hdr=0x80f7700, flags=2124, chflags=150) at copy.c:741
#7  0x080536d6 in mutt_display_message (cur=0x80f7700) at commands.c:146
#8  0x0805c34f in mutt_index_menu () at curs_main.c:1155
#9  0x08071730 in main (argc=3, argv=0xbfbffa34) at main.c:948
#10 0x0804a882 in ___start ()