| Summary: | [abrt] codeblocks-12.11-2.fc20: Unlock: Process /usr/bin/codeblocks was killed by signal 11 (SIGSEGV) | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Fang Junwei <fjw201198> | ||||||||||||||||||||||||
| Component: | codeblocks | Assignee: | Dan Horák <dan> | ||||||||||||||||||||||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||||||||||||
| Priority: | unspecified | ||||||||||||||||||||||||||
| Version: | 20 | CC: | 52wz1h, andrei.dragomirescu, ChristopherLeeUS, cristian.ciupitu, dan, dimityr_7, efix.fx, ekuric, gbonnema, hk.stefansson, i, isaiasc3, kpusmo, kschueff.t, mithrial, moerbius, mstawiarski, nieric, novatw, rfilippetti1, root-kits, s2, serega.belarus, shawnx, sparsa.roychowdhury, thegreatgotz | ||||||||||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||||||||||||
| OS: | Unspecified | ||||||||||||||||||||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/68b9227c12ad040d932efb8b7b2b4396dda5bce1 | ||||||||||||||||||||||||||
| Whiteboard: | abrt_hash:51f190bffe56627bd175e83eb33b1fa2a9dfaa02 | ||||||||||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||||||||||
| Last Closed: | 2015-06-30 12:27:16 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
Fang Junwei
2013-11-21 01:00:16 UTC
Created attachment 826902 [details]
File: backtrace
Created attachment 826903 [details]
File: cgroup
Created attachment 826904 [details]
File: core_backtrace
Created attachment 826905 [details]
File: dso_list
Created attachment 826906 [details]
File: environ
Created attachment 826907 [details]
File: exploitable
Created attachment 826908 [details]
File: limits
Created attachment 826909 [details]
File: maps
Created attachment 826910 [details]
File: open_fds
Created attachment 826911 [details]
File: proc_pid_status
Created attachment 826912 [details]
File: var_log_messages
chaque demmarrage de Skype et il m'est un son qui ne cesse pas de s'arreter... reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.11.10-300.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: Process /usr/bin/codeblocks was killed by signal 11 (SIGSEGV) runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I opened up an existing project with a very simple program in it and no external dependencies. When I closed the program it dumped core. I had not done anything special, not even compiled, just checked out sources that were already open when I opened the project. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.12.5-302.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Opened the app, then closed it with no modification, and the crash message appeared. reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.12.6-300.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: just exited the application reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/bin/codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.12.6-300.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: suddenly crashed when I want to close the program reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.12.6-300.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I saved my session and exited CodeBlocks. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.13.3-201.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Incident survenu lors de la fermeture de code::blocks. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.13.3-201.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Open and close code::blocks via the menu. reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.13.3-201.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 This bug has been fixed in 13.12 version which is not pushed to f20. Dan, any plan? Another user experienced a similar problem: First time running the application, ran a template program and exited reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/bin/codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.13.6-200.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: just installed codeblocks, noticed an error found in package codeblocks reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.13.9-200.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: The problem occured when I closed codeblocks. Maybe I should mention that I started the program in a terminal window. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.15.6-200.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Me too. :/ According to ABRT it happened to me too when I closed codeblocks after a debug session of a very simple C program (hello world). Another user experienced a similar problem: The problem occured when I was simply closing the window. In point of fact, I didn't know that there was a problem at all before the bug report tool popped up. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: codeblocks crash_function: Unlock executable: /usr/bin/codeblocks kernel: 3.17.8-200.fc20.x86_64 package: codeblocks-12.11-2.fc20 reason: codeblocks killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |