GNOME Bugzilla – Bug 465058
Segfault when saving account settings
Last modified: 2011-02-19 00:05:17 UTC
Forwarding this from a downstream bug report: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=251391 Description of problem: I'm getting the following traceback when clicking "Ok" after viewing my account settings.
+ Trace 153977
Version-Release number of selected component (if applicable): evolution-2.11.6.1-1.fc8
Here's the offending function: static int folder_info_cmp (const void *ap, const void *bp) { const CamelFolderInfo *a = ((CamelFolderInfo **)ap)[0]; const CamelFolderInfo *b = ((CamelFolderInfo **)bp)[0]; return strcmp (a->full_name, b->full_name); } Looks like another case of not checking for NULL before calling strcmp().
Created attachment 93377 [details] [review] Proposed patch This patch should fix the immediate problem. I'm not sure whether it's valid for folder full names to be NULL, so this could just be fixing a symptom of a deeper problem.
Sankar/Varadhan?
(In reply to comment #2) > Created an attachment (id=93377) [edit] > Proposed patch > > This patch should fix the immediate problem. > > I'm not sure whether it's valid for folder full names to be NULL, so this could > just be fixing a symptom of a deeper problem. > folder full names shouldn't be NULL. I understand that the patch would fix the crash, however, we need to find out why the folder full names were NULL. Marking the patch as "needs-work".
Bumping version to a stable release.
Does the patch still hold the value ?
Matthew, ping, would you please check if the patch still holds good for master (2.91.6) ?
Patch still applies, but I agree with comment #4. Searching the currently open bugs for comments containing "folder_info_cmp" (and this includes stack traces), this bug is the only hit. So whatever caused a NULL CamelFolderInfo to be passed to this function seems to have been fixed already. This bug is over three years old now. Let's just close it as OBSOLETE.