Bug 851210
Summary: | [abrt] will-crash-0.2-1.fc17: main: Process /usr/bin/will_abort was killed by signal 6 (SIGABRT) | ||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | ABRT <crash-catcher> | ||||||||||||||||||||
Component: | will-crash | Assignee: | Martin Milata <mmilata> | ||||||||||||||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||||||||
Priority: | unspecified | ||||||||||||||||||||||
Version: | 19 | Keywords: | Reopened | ||||||||||||||||||||
Target Milestone: | --- | ||||||||||||||||||||||
Target Release: | --- | ||||||||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||||||||
OS: | Unspecified | ||||||||||||||||||||||
Whiteboard: | abrt_hash:348f14424bdf6726346c74fe5329c980cc19c899 | ||||||||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||||||||
Clone Of: | Environment: | ||||||||||||||||||||||
Last Closed: | 2015-02-17 14:25:50 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
ABRT
2012-08-23 13:51:23 UTC
Created attachment 606579 [details]
File: core_backtrace
Created attachment 606580 [details]
File: environ
Created attachment 606581 [details]
File: limits
Created attachment 606582 [details]
File: cgroup
Created attachment 606583 [details]
File: maps
Created attachment 606584 [details]
File: dso_list
Created attachment 606585 [details]
File: var_log_messages
Created attachment 606586 [details]
File: open_fds
As usually ... backtrace_rating: 4 Package: will-crash-0.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Run will_abort and it aborts()! backtrace_rating: 4 Package: will-crash-0.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) This crash was intentionally generated with pre-update F17 abrt, but is being reported with testing update. Should work as expected even with this situation. backtrace_rating: 4 Package: will-crash-0.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) ABRT Testing backtrace_rating: 4 Package: will-crash-0.2-1.fc17 OS Release: Fedora release 18 (Spherical Cow) Report against a new version of glibc in F17 backtrace_rating: 4 Package: will-crash-0.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Description of problem: ABRT dup comment test .... Version-Release number of selected component: will-crash-0.2-1.fc17 Additional info: backtrace_rating: 4 cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.6.10-2.fc17.x86_64 uid: 18601 Truncated backtrace: [New LWP 19965] Core was generated by `will_segfault'. Program terminated with signal 11, Segmentation fault. #0 main () at will_segfault.c:7 7 } Thread 1 (LWP 19965): #0 main () at will_segfault.c:7 i = <error reading variable i (Cannot access memory at address 0x0)> From To Syms Read Shared Object Library 0x0000003ea361ef60 0x0000003ea375f7a0 Yes /lib64/libc.so.6 0x0000003ea3200b20 0x0000003ea321a2e9 Yes /lib64/ld-linux-x86-64.so.2 $1 = 0x0 No symbol "__glib_assert_msg" in current context. rax 0xf 15 rbx 0x0 0 rcx 0x3ea36e4950 269029886288 rdx 0x3ea39b2ae0 269032827616 rsi 0x7fc6b5add000 140491428319232 rdi 0xffffffff 4294967295 rbp 0x0 0x0 rsp 0x7fff6c9ba310 0x7fff6c9ba310 r8 0xffffffff 4294967295 r9 0x0 0 r10 0x22 34 r11 0x246 582 r12 0x40042c 4195372 r13 0x7fff6c9ba3f0 140735015527408 r14 0x0 0 r15 0x0 0 rip 0x40041e 0x40041e <main+14> eflags 0x10246 [ PF ZF IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 Dump of assembler code for function main: 0x0000000000400410 <+0>: sub $0x8,%rsp 0x0000000000400414 <+4>: mov $0x4005e0,%edi 0x0000000000400419 <+9>: callq 0x4003f0 <puts@plt> => 0x000000000040041e <+14>: mov 0x0,%eax 0x0000000000400425 <+21>: add $0x8,%rsp 0x0000000000400429 <+25>: retq End of assembler dump. ABRT dup comment test .... backtrace_rating: 4 Package: will-crash-0.2-1.fc17 OS Release: Fedora release 17 (Beefy Miracle) Description of problem: Dup another test ... Version-Release number of selected component: will-crash-0.2-1.fc17 Additional info: backtrace_rating: 4 cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.6.10-2.fc17.x86_64 uid: 18601 Truncated backtrace: [New LWP 27086] Core was generated by `will_segfault'. Program terminated with signal 11, Segmentation fault. #0 main () at will_segfault.c:7 7 } Thread 1 (LWP 27086): #0 main () at will_segfault.c:7 i = <error reading variable i (Cannot access memory at address 0x0)> From To Syms Read Shared Object Library 0x0000003ea361ef60 0x0000003ea375f7a0 Yes /lib64/libc.so.6 0x0000003ea3200b20 0x0000003ea321a2e9 Yes /lib64/ld-linux-x86-64.so.2 $1 = 0x0 No symbol "__glib_assert_msg" in current context. rax 0xf 15 rbx 0x0 0 rcx 0x3ea36e4950 269029886288 rdx 0x3ea39b2ae0 269032827616 rsi 0x7f680ef51000 140084904267776 rdi 0xffffffff 4294967295 rbp 0x0 0x0 rsp 0x7fff8d1023d0 0x7fff8d1023d0 r8 0xffffffff 4294967295 r9 0x0 0 r10 0x22 34 r11 0x246 582 r12 0x40042c 4195372 r13 0x7fff8d1024b0 140735560033456 r14 0x0 0 r15 0x0 0 rip 0x40041e 0x40041e <main+14> eflags 0x10246 [ PF ZF IF RF ] cs 0x33 51 ss 0x2b 43 ds 0x0 0 es 0x0 0 fs 0x0 0 gs 0x0 0 Dump of assembler code for function main: 0x0000000000400410 <+0>: sub $0x8,%rsp 0x0000000000400414 <+4>: mov $0x4005e0,%edi 0x0000000000400419 <+9>: callq 0x4003f0 <puts@plt> => 0x000000000040041e <+14>: mov 0x0,%eax 0x0000000000400425 <+21>: add $0x8,%rsp 0x0000000000400429 <+25>: retq End of assembler dump. Description of problem: Dup another test ... Version-Release number of selected component: will-crash-0.2-1.fc17 Additional info: backtrace_rating: 4 cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.6.10-2.fc17.x86_64 reason: Process /usr/bin/will_segfault was killed by signal 11 (SIGSEGV) uid: 18601 Dup another test ... backtrace_rating: 4 blah: cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.6.10-2.fc17.x86_64 package: will-crash-0.2-1.fc17 reason: Process /usr/bin/will_segfault was killed by signal 11 (SIGSEGV) uid: 18601 This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 WONTFIX if it remains open with a Fedora 'version' of '17'. 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 prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. Another user experienced a similar problem: dunno (really) reporter: libreport-2.1.9.10.g4cbb backtrace_rating: 4 cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.11.6-200.fc19.x86_64 package: will-crash-0.4-1.fc19 reason: will_segfault killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Test, please ignore. reporter: libreport-2.1.9.29.g0b35 backtrace_rating: 4 cmdline: will_abort crash_function: main executable: /usr/bin/will_abort kernel: 3.11.7-200.fc19.x86_64 package: will-crash-0.4-1.fc19 reason: will_abort killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000 Created attachment 891177 [details]
File: /etc/passwd
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. 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 19 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 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 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. |