Red Hat Bugzilla – Bug 685034
[PATCH] (SIGABRT) FindGoodServer, OpenUserMailbox, exchange_mapi_set_flags
Last modified: 2015-09-27 22:21:42 EDT
Description of problem: abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: evolution component: evolution executable: /usr/bin/evolution kernel: 2.6.32-71.18.2.el6.x86_64 rating: 0 reason: Process /usr/bin/evolution was killed by signal 6 (SIGABRT) time: 1299708749 uid: 500 Version-Release number of selected component (if applicable): Red Hat Enterprise Linux Server release 6.0 (Santiago) evolution-2.28.3-10.el6 How reproducible: Random crash Steps to Reproduce: 1. 2. 3. Actual results: evolution crashed. Expected results: evolution should not crashed. Additional info:
Created attachment 484364 [details] Backtrace, Dissassembly
Thanks for a bug report. This crash is from openchange. The issue is fixed with a test package from a build [1]. Please give it a try. [1] https://brewweb.devel.redhat.com/taskinfo?taskID=3178364
Created attachment 484388 [details] oc patch
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
This request was not resolved in time for the current release. Red Hat invites you to ask your support representative to propose this request, if still desired, for consideration in the next release of Red Hat Enterprise Linux.
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development. This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comparing the patch for OpenChange 0.9 to the rebased OpenChange 1.0 code, it looks the issue was fixed by the rebase. Or at least that particular variable in that particular function seems to be allocated and freed correctly now, so I'm marking this as MODIFIED. SanityOnly seems the only way to verify this.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0515.html