GNOME Bugzilla – Bug 488564
crash in Evolution Mail and Calendar: Just started tool. Selec...
Last modified: 2012-10-15 23:51:18 UTC
What were you doing when the application crashed? Just started tool. Selected "Calendars". Immediate crash. Distribution: Solaris Express Community Edition snv_75a X86 Gnome Release: 2.20.0 2007-09-24 (Sun Microsystems, Inc.) BugBuddy Version: 2.20.0 X Vendor: Sun Microsystems, Inc. X Vendor Release: 10300000 Selinux: No Accessibility: Disabled GTK+ Theme: blueprint Icon Theme: blueprint Memory status: size: 126681088 vsize: 126681088 resident: 48807936 share: 393216 rss: 48807936 rss_rlim: 0 CPU usage: start_time: 0 rtime: 115 utime: 1048325 stime: 101780 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/evolution' (no debugging symbols found) sol-thread active. Retry #1: Retry #2: Retry #3: Retry #4: [New LWP 1 ] [New Thread 1 (LWP 1)]
+ Trace 171655
Thread 1 (LWP 1)
Thread 6 (Thread 4 ): #-1 0xfe24e8eb in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 5 (Thread 3 ): #-1 0xfe24e8eb in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 4 (LWP 3 ): #-1 0xfe24e8eb in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 3 (LWP 4 ): #-1 0xfe24e8eb in __lwp_park () from /usr/lib/libc.so.1 No symbol table info available. Thread 2 (Thread 1 (LWP 1)): #-1 0xfe252897 in _waitid () from /usr/lib/libc.so.1 No symbol table info available. Thread 1 (LWP 1 ): #-1 0xfe252897 in _waitid () from /usr/lib/libc.so.1 No symbol table info available. #-1 0xfe252897 in _waitid () from /usr/lib/libc.so.1
*** Bug 494762 has been marked as a duplicate of this bug. ***
*** Bug 492667 has been marked as a duplicate of this bug. ***
*** Bug 497076 has been marked as a duplicate of this bug. ***
*** Bug 492693 has been marked as a duplicate of this bug. ***
*** Bug 493881 has been marked as a duplicate of this bug. ***
*** Bug 496372 has been marked as a duplicate of this bug. ***
*** Bug 489959 has been marked as a duplicate of this bug. ***
Reporters: Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! This is cropping up in a variety of programs, but always with the same top crashstack
+ Trace 178121
and always on Solaris Express Community Edition. I've spotted versions between 75a and 77. Reporters: If you can no longer reproduce this with a later version of Solaris Express (or at least of the glib packages), then can you please report that as well. Thanks!
*** Bug 499243 has been marked as a duplicate of this bug. ***
Although all the bugs are caused by accessing NULL pointer which will cause applications to crash on Solaris, but they are not the same bug. Because the reason causing the applications to access NULL pointer is different for applications. So these bugs should be reopened and fixed individually. Another reason for not fixing it in glib is because a NULL pointer is a potential bug in software, we should pay attention to it but not ignore it.
*** Bug 499524 has been marked as a duplicate of this bug. ***
*** Bug 501674 has been marked as a duplicate of this bug. ***
*** Bug 505324 has been marked as a duplicate of this bug. ***
*** Bug 513882 has been marked as a duplicate of this bug. ***
*** Bug 515559 has been marked as a duplicate of this bug. ***
*** Bug 510703 has been marked as a duplicate of this bug. ***
*** Bug 503558 has been marked as a duplicate of this bug. ***
*** Bug 520683 has been marked as a duplicate of this bug. ***
*** Bug 523421 has been marked as a duplicate of this bug. ***
*** Bug 521354 has been marked as a duplicate of this bug. ***
*** Bug 524801 has been marked as a duplicate of this bug. ***
*** Bug 524949 has been marked as a duplicate of this bug. ***
*** Bug 525734 has been marked as a duplicate of this bug. ***
*** Bug 525862 has been marked as a duplicate of this bug. ***
*** Bug 527056 has been marked as a duplicate of this bug. ***
*** Bug 528040 has been marked as a duplicate of this bug. ***
*** Bug 529645 has been marked as a duplicate of this bug. ***
*** Bug 500912 has been marked as a duplicate of this bug. ***
*** Bug 466077 has been marked as a duplicate of this bug. ***
*** Bug 531671 has been marked as a duplicate of this bug. ***
*** Bug 532318 has been marked as a duplicate of this bug. ***
*** Bug 533047 has been marked as a duplicate of this bug. ***
*** Bug 543114 has been marked as a duplicate of this bug. ***
*** Bug 511242 has been marked as a duplicate of this bug. ***
*** Bug 599844 has been marked as a duplicate of this bug. ***
(In reply to comment #10) > Although all the bugs are caused by accessing NULL pointer which will cause > applications to crash on Solaris, but they are not the same bug. Because the > reason causing the applications to access NULL pointer is different for > applications. So these bugs should be reopened and fixed individually. > > Another reason for not fixing it in glib is because a NULL pointer is a > potential bug in software, we should pay attention to it but not ignore it. So you propose to "un-dup" the duplicates and reassign things back to the applications? I would propose such an approach as well…
nothing to be done in glib here.