Version-Release number of selected component: gdb-7.6.50.20130731-16.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: gdb --interpreter mi2 --nx crash_function: vasprintf executable: /usr/bin/gdb kernel: 3.12.5-302.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #7 vasprintf at /usr/include/bits/stdio2.h:210 #8 xstrvprintf at ../../gdb/common/common-utils.c:130 #9 xstrprintf at ../../gdb/common/common-utils.c:121 #10 commandline_from_pid at ../../gdb/common/linux-osdata.c:167 #11 linux_xfer_osdata_processes at ../../gdb/common/linux-osdata.c:342 #12 linux_nat_xfer_osdata at ../../gdb/linux-nat.c:4632 #13 linux_xfer_partial at ../../gdb/linux-nat.c:4647 #14 linux_nat_xfer_partial at ../../gdb/linux-nat.c:4236 #15 target_xfer_partial at ../../gdb/target.c:1733 #16 target_read_partial at ../../gdb/target.c:2020
Created attachment 844113 [details] File: backtrace
Created attachment 844114 [details] File: cgroup
Created attachment 844115 [details] File: core_backtrace
Created attachment 844116 [details] File: dso_list
Created attachment 844117 [details] File: environ
Created attachment 844118 [details] File: limits
Created attachment 844119 [details] File: maps
Created attachment 844120 [details] File: open_fds
Created attachment 844121 [details] File: proc_pid_status
Created attachment 844122 [details] File: var_log_messages
Thanks for the bug report. By analysing the backtrace I really don't see anything wrong with the function calls. For example, one can see that in commandline_from_pid the PID is correctly provided: #10 0x00000000004aac06 in commandline_from_pid (pid=1296) ... And then, right when commandline_from_pid invokes xstrprintf: #9 0x00000000006a0529 in xstrprintf (format=format@entry=0x78c173 "/proc/%lld/cmdline") .. We see that the format is correctly passed. Going a bit up in the stack, we see that the error (SIGABRT) is actually caused because malloc found a corrupted double-linked list: #3 0x000000355e47bbc7 in malloc_printerr (action=<optimized out>, str=0x355e579dda "corrupted double-linked list", ptr=<optimized out>) ... Which leads me to think that this is not a GDB bug, but rather something else strangely happening on the glibc/Linux side... Would you happen to have the corefile generated by this error? Or maybe some reproducer, so that we can try to replicate the issue? Thanks.
Created attachment 850623 [details] All data collected by ABRT
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.