Description of problem: Testing bugzilla reporting Version-Release number of selected component: will-crash-0.4-1.fc18 Additional info: reporter: libreport-2.1.9.7.g7d03.dirty backtrace_rating: 4 cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.10.11-100.fc18.x86_64 runlevel: N 5 type: CCpp uid: 0 Truncated backtrace: [New LWP 7027] warning: .dynamic section for "/lib64/libc.so.6" is not at the expected address (wrong library or version mismatch?) warning: .dynamic section for "/lib64/ld-linux-x86-64.so.2" is not at the expected address (wrong library or version mismatch?) warning: Could not load shared library symbols for number of relative relocations: %lu . Do you need "set solib-search-path" or "set sysroot"? Core was generated by `will_segfault'. Program terminated with signal 11, Segmentation fault. #0 main () at will_segfault.c:7 7 } Thread 1 (LWP 7027): #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 0x00007f0a838c31e0 0x00007f0a83a04840 Yes /lib64/libc.so.6 0x00007f0a83c5cb28 0x00007f0a83c763e1 Yes /lib64/ld-linux-x86-64.so.2 No number of relative relocations: %lu $1 = 0x0 No symbol "__glib_assert_msg" in current context. rax 0xf 15 rbx 0x0 0 rcx 0x7f0a83982760 139683134187360 rdx 0x7f0a83c57a30 139683137157680 rsi 0x7f0a83e7a000 139683139395584 rdi 0x1 1 rbp 0x0 0x0 rsp 0x7fff371c1a20 0x7fff371c1a20 r8 0xffffffff 4294967295 r9 0x0 0 r10 0x22 34 r11 0x246 582 r12 0x40045c 4195420 r13 0x7fff371c1b00 140734117976832 r14 0x0 0 r15 0x0 0 rip 0x40044e 0x40044e <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 st0 *value not available* st1 *value not available* st2 *value not available* st3 *value not available* st4 *value not available* st5 *value not available* st6 *value not available* st7 *value not available* fctrl *value not available* fstat *value not available* ftag *value not available* fiseg *value not available* fioff *value not available* foseg *value not available* fooff *value not available* fop *value not available* xmm0 *value not available* xmm1 *value not available* xmm2 *value not available* xmm3 *value not available* xmm4 *value not available* xmm5 *value not available* xmm6 *value not available* xmm7 *value not available* xmm8 *value not available* xmm9 *value not available* xmm10 *value not available* xmm11 *value not available* xmm12 *value not available* xmm13 *value not available* xmm14 *value not available* xmm15 *value not available* mxcsr *value not available* Dump of assembler code for function main: 0x0000000000400440 <+0>: sub $0x8,%rsp 0x0000000000400444 <+4>: mov $0x400600,%edi 0x0000000000400449 <+9>: callq 0x400410 <puts@plt> => 0x000000000040044e <+14>: mov 0x0,%eax 0x0000000000400455 <+21>: add $0x8,%rsp 0x0000000000400459 <+25>: retq End of assembler dump. Potential duplicate: bug 851210
Created attachment 819185 [details] File: backtrace
Created attachment 819186 [details] File: cgroup
Created attachment 819187 [details] File: core_backtrace
Created attachment 819188 [details] File: dead.letter
Created attachment 819189 [details] File: dso_list
Created attachment 819190 [details] File: environ
Created attachment 819191 [details] File: limits
Created attachment 819192 [details] File: maps
Created attachment 819193 [details] File: open_fds
Created attachment 819194 [details] File: proc_pid_status
Testing bugzilla reporting 2 reporter: libreport-2.1.9.7.g7d03.dirty backtrace_rating: 4 cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.10.11-100.fc18.x86_64 package: will-crash-0.4-1.fc18 reason: will_segfault killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
Another user experienced a similar problem: Testing bugzilla reporting 2 reporter: libreport-2.1.9.9.gdef1.dirty backtrace_rating: 4 cmdline: will_segfault crash_function: main executable: /usr/bin/will_segfault kernel: 3.10.11-100.fc18.x86_64 package: will-crash-0.4-1.fc18 reason: will_segfault killed by SIGSEGV runlevel: N 5 type: CCpp uid: 0
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 18'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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.