GNOME Bugzilla – Bug 240922
mail part crashes when I start the client
Last modified: 2003-05-16 17:38:21 UTC
Package: Evolution Priority: Normal Version: 1.2.3 Synopsis: mail part crashes when I start the client Bugzilla-Product: Evolution Bugzilla-Component: Mailer Description: Description of Problem: When I start it up the mail part crashes Steps to reproduce the problem: 1. Start thge client 2. 3. Actual Results: Expected Results: How often does this happen? Always Additional Information: Debugging Information: Backtrace was generated from '/usr/lib/evolution/evolution-mail' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 699)] [New Thread 32769 (LWP 749)] [New Thread 16386 (LWP 750)] [New Thread 32771 (LWP 751)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...0x41132b89 in wait4 () from /lib/libc.so.6
+ Trace 35709
Thread 4 (Thread 32771 (LWP 751))
Thread 3 (Thread 16386 (LWP 750))
Thread 1 (Thread 16384 (LWP 699))
Unknown reporter: generallee@c64.org, changed to bugbuddy-import@ximian.com. Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
looks like a bug in libc's dlopen *shrug* could also be memory corruption. if it's memory corruption, it could be anywhere. besides, the backtrace is pretty useless (blame bugbuddy). nothing I can do with this bug report other than close it as INVALID
*** This bug has been marked as a duplicate of 243160 ***