Topic says it all. I found acertain article in be.comp.hardware which makes pan 
crash when  trying to follow-up to it, that means, at  the very pressing of the 'F' 
button (not when actually sending a reply).

Here are the headers:

Path: 
uni-berlin.de!fu-berlin.de!news.netcologne.de!skynet.be!skynet.be!louie!not-for-mail
From:  "Pascal Houben" <pascal.houben@skynet.be>
Newsgroups: be.comp.hardware
References:  <3cd17f00$0$10243$afc38c87@sisyphus.news.be.easynet.net>
Subject: Re: IBM Deskstar 60 GXP - 40GB slechte reeks!
Date: Thu, 2 May 2002 20:20:21 +0200
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Lines: 41
Message-ID: <3cd18365$0$6976$ba620e4c@news.skynet.be>
Organization: -= Skynet Usenet Service =-
NNTP-Posting-Host: 80.200.60.47
X-Trace: 1020363621 reader1.news.skynet.be 6976 80.200.60.47
X-Complaints-To: abuse@skynet.be
Xref: uni-berlin.de be.comp.hardware:14626

Special thanks go to knode, because Pan didn't show any headers ;)

Here is a back trace:


Script started on Fri May  3 17:21:08 2002
bash: unalias: `rm': not an alias
yalu@dionysos:~$ uname -a
Linux dionysos 2.4.18 #6 Thu Apr 25 19:29:29 CEST 2002 i686 unknown
yalu@dionysos:~$ gd k-pixbuf-c                                    gdb 
gdb        gdbserver
yalu@dionysos:~$ gdb pan
GNU gdb 2002-04-01-cvs
Copyright 2002 Free Software Foundation, Inc. 
GDB is free software, covered by the GNU General Public License, and you are 
welcome to change it and/or distribute copies of it under certain conditions. 
Type "show copying" to see the conditions. 
There is absolutely no warranty for GDB.  Type "show warranty" for details. 
This GDB was configured as "i386-linux"... 
(gdb) handle SIGUSR1 nostop noprint
Signal        Stop	Print	Pass to program	Description
SIGUSR1       No	No	Yes		User defined signal 1
(gdb)  handle SIG32 nostop noprint
Signal        Stop	Print	Pass to program	Description
SIG32         No	No	Yes		Real-time event 32
(gdb) r --disable-crash-dialog
Starting program: /home/yalu/build/pan/pan/pan --disable-crash-dialog 
/bin/bash: unalias: `rm': not an alias 
[New Thread 1024 (LWP 568)] 
[New Thread 2049 (LWP 569)]
[New Thread 1026 (LWP 570)]
[New Thread 2051 (LWP 571)]
[New Thread 3076 (LWP 572)]

** (pan:568): WARNING **: Invalid UTF-8 sequence encountered
 
** (pan:568): WARNING **: Invalid UTF-8 sequence encountered 
 
** (pan:568): WARNING **: Invalid UTF-8 sequence encountered

** (pan:568): WARNING **: Invalid UTF-8 sequence encountered

** (pan:568): WARNING **: Invalid UTF-8 sequence encountered

** (pan:568): WARNING **: Invalid UTF-8 sequence encountered
 
** (pan:568): WARNING **: Invalid UTF-8 sequence encountered 
 
** (pan:568): WARNING **: Invalid UTF-8 sequence encountered

(pan:568): pan-CRITICAL **: file gui-headers.c: line 71 (find_breakpoint): assertion `is_nonempty_string(str)' failed

(pan:568): pan-CRITICAL **: file gui-headers.c: line 71 (find_breakpoint): assertion `is_nonempty_string(str)' failed

Program received signal SIGSEGV, Segmentation fault. 
[Switching to Thread 1024 (LWP 568)] 
0x4038f8a3 in g_utf8_strlen () from /usr/lib/libglib-2.0.so.0 
(gdb) bt

+ Trace 21672

A debugging session is active.
Do you still want to close the debugger?(y or n) y
yalu@dionysos:~$
Script done on Fri May  3 17:25:11 2002