Steven Vancoillie wrote:
> On Sat, Jun 13, 2009 at 10:20:21PM +0100, Antonio Radici wrote:
>> I forgot to say, if you also attach your .muttdebug0 it will help us a lot,
>> so
>> we need corefile and .muttdebug0. If you manage to tls_socket_close and then
>> generate the core, it would be great =)
>
> I tried to get a core file before (setting ulimit -c unlimited)
> but I dit not get any core dump.
>
> Is it ok to generate the core file from within gdb?
> If so, do I have to set a breakpoint at tls_socket_close or
> just wait until mutt hangs to do generate-core-file in gdb?
>
Ok let's see what we need:
0) /usr/sbin/tcpdump -w dumpimap port 993 (or 143, it depends on what you'ure
using)
1) launch mutt in gdb, set args -d5, so we will also generate .muttdebug0
2) run, then ctrl+C
3) break mutt_ssl_gnutls.c:135
(you should have the mutt sources in your $CWD, if you don't please apt-get
source mutt)
just for the records, this is where I want to break:
133 if (gnutls_error_is_fatal(ret) == 1)
134 {
135 mutt_error ("tls_socket_write (%s)", gnutls_strerror (ret));
4) as soon as you will get that error mutt will break, then launch
generate-core-file
once you're done please send us
1) dumpimap (the tcpdump of your imap conn)
2) .muttdebug0
3) the bzip2-ed corefile
please note that the corefile could contain your pass, so remember to change it
before or afterwards :-)
I look foward to your answer
Cheers
Antonio
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
