[Users] [Bug 3069] New: Claws-mail GIT crashes when reading NNTP

noreply at thewildbeast.co.uk noreply at thewildbeast.co.uk
Sat Jan 25 20:11:25 CET 2014


            Bug ID: 3069
           Summary: Claws-mail GIT crashes when reading NNTP
    Classification: Unclassified
           Product: Claws Mail
           Version: GIT
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: NNTP
          Assignee: users at lists.claws-mail.org
          Reporter: fragabr at gmail.com

I'm using Claws-mail (version 3.9.3-11-g845d06) with libetpan (latest GIT) and
sometimes (not always) when I select a newsgroup it crashes. Here's the

folderview.c:2157:Folder gmane.announce is selected
folderview.c:2173:Opening folder gmane.announce...
folder.c:2164:Scanning folder gmane.announce for cache changes.
** Message: Account 'NNTP': Connecting to NNTP server: news.gmane.org:119...

[New Thread 0x7fffe25dd700 (LWP 21222)]
nntp-thread.c:248:found nntp 0xac9800

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffe25dd700 (LWP 21222)]
0x0000000000d6c9c0 in ?? ()
(gdb) bt
#0  0x0000000000d6c9c0 in ?? ()
#1  0x00007ffff0a7e760 in mailstream_logger_internal (size=20,
buffer=0x7ffff0ae7fab "<<<<<<< read <<<<<<\n", direction=0, is_stream_data=0,
s=0x7fffdc0024b0) at mailstream_low.c:408
#2  mailstream_low_read (s=0x7fffdc0024b0, buf=0x7fffdc002550, count=<optimized
out>) at mailstream_low.c:232
#3  0x00007ffff0a7fb08 in mailstream_feed_read_buffer
(s=s at entry=0x7fffdc0024f0) at mailstream.c:322
#4  0x00007ffff0a7dd50 in mailstream_read_line_append (stream=0x7fffdc0024f0,
line=line at entry=0xed2c1e0) at mailstream_helper.c:101
#5  0x00007ffff0a7dda1 in mailstream_read_line (stream=<optimized out>,
line=line at entry=0xed2c1e0) at mailstream_helper.c:62
#6  0x00007ffff0a7ddc9 in mailstream_read_line_remove_eol (stream=<optimized
out>, line=0xed2c1e0) at mailstream_helper.c:116
#7  0x00007ffff0ab8309 in read_line (f=0xac9800, f=0xac9800) at newsnntp.c:1832
#8  newsnntp_connect (f=0xac9800, s=<optimized out>) at newsnntp.c:195
#9  0x0000000000619c60 in connect_run (op=0xed45bf0) at nntp-thread.c:334
#10 0x0000000000642282 in thread_run (data=0xecfdf90) at
#11 0x00007ffff0d21003 in start_thread () from /lib64/libpthread.so.0
#12 0x00007fffeef2dbcd in clone () from /lib64/libc.so.6


If you need more information, just ask.

You are receiving this mail because:
You are the assignee for the bug.

More information about the Users mailing list