mail/evolution-devel crashed w/ seg fault (looks like thread issue)

[Joe Marcus Clarke]

On Mon, 2003-05-12 at 23:29, Mezz bsdforums.org wrote:
> Here's how I crashed it. When, I waited for evolution to connect the POP 
> server for like over two minutes, then I pressed the cancel button and 
> crashed with the seg fault. It happens at the everytime if I touch the canel 
> button. I think, it looks like it's thread issue again, but I don't know.. 
> Might be from gtkhtml3 or else? Right now, I am trying to figure why it will 
> not connect to the POP account, which I have no problem with the Opera 7's 
> mail (M2) client on the same machine.

I don't think this is a threading issue.  Evo and friends are not
packaged using the "bad" version of libtool.  Plus, I have had no
trouble with my -CURRENT installation.  Of course, I don't use it for
anything but simple testing.

> 
> By default, it's weird that I already have the permission issues in my home 
> directory at ~/evolution/ such as can't open/delete a welcome mail that was 
> included. Must be beta version.. I will fix them after this email.
> 
> Anyway, I ran it under the gdb and here's info:

This looks like a genuine memory issue.  Does the problem go away with
aj?

> 
> =================================
> (gdb) r
> Starting program: /usr/X11R6/bin/evolution-1.3
> 
> (evolution-1.3:70294): GConf-CRITICAL **: file gconf-listeners.c: line 339 
> (ltable_insert): assertion `gconf_valid_key(where, NULL)' failed
> 
> (evolution-1.3:70294): camel-WARNING **: Invalid root: 
> '//usr/home/mezz/evolution/local/Drafts/mbox.ibex.index'
> 
> (evolution-1.3:70294): camel-WARNING **: version: TEXT.000 (TEXT.000)
> 
> (evolution-1.3:70294): camel-WARNING **: block size: 1024 (1024) OK
> 
> (evolution-1.3:70294): camel-WARNING **: free: 0 (0 add size < 1024) OK
> 
> (evolution-1.3:70294): camel-WARNING **: last: 6144 (6144 and size: 1024) 
> BAD
> 
> (evolution-1.3:70294): camel-WARNING **: flags: unSYNC
> file:///usr/local/share/xml/catalog:1: error: Start tag expected, '<' not 
> found
> CATALOG "sdocbook/catalog"

Wonder what's trying to read the catalog...?  Can you try setting
XML_CATALOG_FILES to "/usr/local/share/sk/catalog
/usr/local/share/sk/docbook/catalog" and see if this message goes away? 
Are you sure this is coming from Evo?  I've never seen it.

> 
> warning: failed to load external entity 
> "/usr/home/mezz/evolution/config/storage-set-view-expanded:default"
> warning: failed to load external entity 
> "/usr/home/mezz/evolution/views/mail/galview.xml"
> warning: failed to load external entity 
> "/usr/home/mezz/evolution/filters.xml"
> warning: failed to load external entity 
> "/usr/home/mezz/evolution/filters.xml"
> 
> (evolution-1.3:70294): camel-pop3-provider-WARNING **: Bad server response:  
> DELE, LIST, LAST, NOOP, RETR, RSET, STAT, TOP, UIDL or QUIT
> 
> 
> Program received signal SIGBUS, Bus error.
> g_hash_nodes_destroy (hash_node=0xd0d0d0d0, key_destroy_func=0,
>     value_destroy_func=0) at ghash.c:691
> 691     ghash.c: No such file or directory.
>         in ghash.c
> 
> (gdb) bt
> #0  g_hash_nodes_destroy (hash_node=0xd0d0d0d0, key_destroy_func=0,
>     value_destroy_func=0) at ghash.c:691
> #1  0x291ed30c in g_hash_table_destroy (hash_table=0x8744860) at ghash.c:178
> #2  0x295f6b1e in camel_folder_change_info_free (info=0x87364c0)
>     at camel-folder.c:2150
> #3  0x295f25ef in camel_folder_finalize (object=0xd0d0d0d0)
>     at camel-folder.c:201
> #4  0x29613e3c in camel_object_unref (vo=0x8594c00) at camel-object.c:500
> #5  0x298364e0 in camel_pop3_folder_new (parent=0xd0d0d0d0, ex=0x8746918)
>     at camel-pop3-folder.c:134
> #6  0x298395a2 in get_folder (store=0xd0d0d0d0, folder_name=0x8594c00 "",
>     flags=0, ex=0x8746918) at camel-pop3-store.c:628
> #7  0x29623f28 in get_inbox (store=0x0, ex=0xd0d0d0d0) at camel-store.c:454
> #8  0x29623f69 in camel_store_get_inbox (store=0x8594c00, ex=0xd0d0d0d0)
>     at camel-store.c:471
> #9  0x29575ee7 in mail_tool_get_inbox (
>     url=0xd0d0d0d0 <Error reading address 0xd0d0d0d0: Bad address>,
>     ex=0x8594c00) at mail-tools.c:81
> #10 0x2956cd28 in fetch_mail_fetch (mm=0x8746900) at mail-ops.c:299

Looks like things start to break down here.  The _mail_msg->source_uri
passed to fetch_mail_fetch() has been alloc'd but not assigned, or
free'd.  This is a bug.  I'd file this with Ximian along with the full
stack trace, and exactly what you did to reproduce it.

Joe

> #11 0x2956ac99 in mail_msg_received (e=0x81d2800, msg=0x8746900, data=0x0)
>     at mail-mt.c:503
> #12 0x2814c666 in thread_received_msg (e=0x8750080, m=0xd0d0d0d0)
>     at e-msgport.c:617
> ---Type <return> to continue, or q <return> to quit---
> #13 0x2814c803 in thread_dispatch (din=0x81d2800) at e-msgport.c:698
> #14 0x2932246e in _thread_start ()
>     at /usr/src/lib/libc_r/uthread/uthread_create.c:275
> =================================
> 
> Cheers,
> Mezz
> 
> _________________________________________________________________
> Add photos to your e-mail with MSN 8. Get 2 months FREE*.  
> http://join.msn.com/?page=features/featuredemail
> 
> _______________________________________________
> freebsd-gnome at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-gnome
> To unsubscribe, send any mail to "freebsd-gnome-unsubscribe at freebsd.org"
-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://lists.freebsd.org/pipermail/freebsd-gnome/attachments/20030513/ce9002af/attachment.bin