[prev in list] [next in list] [prev in thread] [next in thread] 

List:       evolution
Subject:    Re: [Evolution] Infinite read loop bug in Evolution 3.0.3?
From:       Milan Crha <mcrha () redhat ! com>
Date:       2011-10-25 6:45:49
Message-ID: 1319525149.2517.11.camel () localhost
[Download RAW message or body]

On Mon, 2011-10-24 at 11:57 -0600, Zan Lynx wrote:
> And GDB shows the Evolution thread seems to be running around in this area:
> (gdb) bt
> #0  0x0000003f2f02e9be in g_cancellable_is_cancelled () from /lib64/libgio-2.0.so.0
> #1  0x0000003d85a5cd3b in ?? () from /usr/lib64/libcamel-provider-1.2.so.23
> #2  0x0000003d84e4f68a in camel_stream_read () from /usr/lib64/libcamel-1.2.so.23
> #3  0x00007f9bea524e6b in ?? () from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
> #4  0x0000003d84e4f68a in camel_stream_read () from /usr/lib64/libcamel-1.2.so.23
> #5  0x0000003d84e50238 in camel_stream_write_to_stream () from /usr/lib64/libcamel-1.2.so.23
> #6  0x00007f9bea525c35 in camel_imapx_stream_nstring_stream ()
>    from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
> #7  0x00007f9bea528bf2 in imapx_parse_fetch ()
>    from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
> #8  0x00007f9bea532977 in ?? () from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
> #9  0x00007f9bea536516 in ?? () from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
> #10 0x00007f9bea5367e5 in ?? () from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
> #11 0x00007f9bea536c20 in ?? () from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
> #12 0x0000003f2d4683a6 in ?? () from /lib64/libglib-2.0.so.0
> #13 0x000000302b807b31 in start_thread () from /lib64/libpthread.so.0
> #14 0x000000302b4dfd2d in clone () from /lib64/libc.so.6

	Hi,
it will be nice to have it filled as a bug report, but only if you'll
install debug info packages for evolution-data-server and evolution,
because without them your backtrace is quite unusable, because it's hard
to see where exactly the imapx provider is and what/why it is trying to
do. With properly installed debuginfo there should not be any lines like
this in the backtrace:
> #11 0x00007f9bea536c20 in ?? ()
> from /usr/lib64/evolution-data-server/camel-providers/libcamelimapx.so
but it'll show a function name (instead of those ??) and file name with
line number in it.
	Bye,
	Milan

_______________________________________________
evolution-list mailing list
evolution-list@gnome.org
To change your list options or unsubscribe, visit ...
http://mail.gnome.org/mailman/listinfo/evolution-list
[prev in list] [next in list] [prev in thread] [next in thread]