| Summary: | [abrt] evolution-data-server-3.0.2-1.fc15: magazine_chain_pop_head: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV) | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Danny Stieben <dmaxel> | ||||||
| Component: | evolution-data-server | Assignee: | Matthew Barnes <mbarnes> | ||||||
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 15 | CC: | mbarnes, mcrha | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | abrt_hash:033e00571e5642f985aa20744e5a7efc1947c1d8 | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2011-05-31 04:44:02 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
|
Description
Danny Stieben
2011-05-29 22:10:48 UTC
Created attachment 501670 [details]
File: maps
Created attachment 501671 [details]
File: backtrace
Thanks for a bug report. The backtrace doesn't show any information from which I could be able to realize why this happened (it has all debug symbols, it's a nice backtrace, only the information about place of the crash doesn't contain any evolution function), and because you wrote it's a random crash for you, then I'm closing this. An option for investigation would be to run e-addressbook-factory under valgrind and check whether it'll claim any issues with memory during your usual work. You can run it like this: $ G_SLICE=always-malloc valgrind /usr/libexec/e-addressbook-factory &>log.txt and then run evolution from another console. There can be running only one e-addressbook-factory, thus make sure there is not any other running before you invoke this command. The log.txt file may contain the information, if any. |