| Summary: | [abrt] setroubleshoot-server-3.1.8-1.fc17: g_logv: Process /usr/bin/python was killed by signal 5 (SIGTRAP) | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Barry Godusky <bgodusky> | ||||||||||
| Component: | setroubleshoot | Assignee: | Daniel Walsh <dwalsh> | ||||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||
| Priority: | unspecified | ||||||||||||
| Version: | 17 | CC: | dmalcolm, dwalsh, mgrepl | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Unspecified | ||||||||||||
| Whiteboard: | abrt_hash:17c5cd5063b7fadf124fc32badf0c63990acf0c6 | ||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2013-04-24 19:45:54 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
Barry Godusky
2012-03-19 23:17:43 UTC
Created attachment 571240 [details]
File: build_ids
Created attachment 571241 [details]
File: dso_list
Created attachment 571242 [details]
File: maps
Created attachment 571243 [details]
File: backtrace
Dave do you have any ideas? (In reply to comment #5) > Dave do you have any ideas? I'm not sure exactly what this bug is. iirc, SIGTRAP is the signal sent to a process when debugging such a process as a trigger for some watched condition (e.g. a breakpoint) so that the debugger can see the unhandled signal, and then act on it. I see that attachment 571243 [details] shows two threads and an X error. This often means that multiple threads are trying to use the process' connection to the X server, and the conversation is getting garbled. Hope this is helpful |