Bug 802411
| Summary: | [abrt] evolution-3.3.91-1.fc17: g_logv: Process /usr/bin/evolution was killed by signal 5 (SIGTRAP) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Artur Flinta <aflinta> | ||||||||||||||||||
| Component: | evolution | Assignee: | Matthew Barnes <mbarnes> | ||||||||||||||||||
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||
| Version: | 17 | CC: | bdpepple, lucilanga, mbarnes, mcrha, mikhail.v.gavrilov, rick+rhbugzilla | ||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||
| Whiteboard: | abrt_hash:5fe1ba532475ee2cb666102c816a2dceb8660ca0 | ||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||
| Last Closed: | 2012-03-13 09:35:23 UTC | Type: | --- | ||||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||||
| Embargoed: | |||||||||||||||||||||
| Attachments: |
|
||||||||||||||||||||
|
Description
Artur Flinta
2012-03-12 13:48:00 UTC
Created attachment 569398 [details]
File: dso_list
Created attachment 569399 [details]
File: gconf_subtree
Created attachment 569400 [details]
File: build_ids
Created attachment 569401 [details]
File: maps
Created attachment 569402 [details]
File: backtrace
Thanks for a bug report. I moved this upstream as [1]. Please see [1] for any further updates. If possible, please CC yourself there, in case upstream developers will have additional questions. [1] https://bugzilla.gnome.org/show_bug.cgi?id=671969 *** Bug 802419 has been marked as a duplicate of this bug. *** *** Bug 809252 has been marked as a duplicate of this bug. *** interesting because occurs when i open empathy chat window These Crashes occurred at a time https://bugzilla.redhat.com/show_bug.cgi?id=810440 What do these crashes except that they occurred at a time? https://bugzilla.redhat.com/show_bug.cgi?id=802411 https://bugzilla.redhat.com/show_bug.cgi?id=575462 https://bugzilla.redhat.com/show_bug.cgi?id=809809 I do not see anything common for those crashes, maybe some module/library writes into an already freed chunk of memory, causing memory corruption in "random" part of memory, causing crash of an unrelated module (the "random" here means it rewrites part of memory which can belong to any or none module/library). If you can reproduce this with empathy, then I suggest to run it under valgrind and see what it'll show (after some time of usage), I would do it like this: a) close empathy b) install debuginfo packages for empathy (make sure it'll be of the same version as the installed empathy) c) run empathy under valgrind and use it for some time (it'll be significantly slower due to all memory checking): $ G_SLICE=always-malloc valgrind --num-callers=50 empathy &>log.txt Note valgrind can avoid certain kinds of crashes, thus even if it'll not crash after some time then the log can contain information about incorrect memory usage. Created attachment 575907 [details]
valgrind-empathy-log
Please see valgrind log. Created attachment 575911 [details]
valgrind-empathy-log
Created attachment 576168 [details]
valgrind empathy log from another machine
Thanks for the update. The logs are basically the same, except the other machine (the last log) doesn't show uses of uninitialized values from the nouveau driver, but otherwise it shows one invalid write (which can cause memory corruptions) when glib NULL-ifies pointer in a structure which is already freed (I do not see what the structure is, it was freed on a signal notification from libebook (it seems you do not have installed debuginfo package of the same version as is yours evolution-data-server package, because valgrind cannot read debug information for this library), though this might be after an error which is shown few lines above this invalid write. There is no usage of g_nullify_pointer() in evolution-data-server, thus this might come from empathy itself. After this invalid write there are many invalid reads caused by empathy itself. I'm moving this to empathy, same as the upstream bug report. (In reply to comment #17) > I'm moving this to empathy, same as the upstream bug report. Oops, Mikhail, can you open a new bug report against empathy instead, please? I just realized that the upstream bug report is about something different (I didn't read this whole bug carefully before writing comment #17) :-/ This will go? https://bugzilla.redhat.com/show_bug.cgi?id=808736 Yes, it works. Thanks. |