|Summary:||gdb segfaults if working directory was deleted|
|Product:||[Fedora] Fedora||Reporter:||Pavel Zhukov <pzhukov>|
|Component:||gdb||Assignee:||Sergio Durigan Junior <sergiodj>|
|Status:||CLOSED ERRATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||31||CC:||dsmith, jan.kratochvil, keiths, kevinb, pmuldoon, sergiodj|
|Fixed In Version:||gdb-184.108.40.20690824-28.fc31||Doc Type:||If docs needed, set a value|
|Doc Text:||Story Points:||---|
|Last Closed:||2020-02-07 01:51:02 UTC||Type:||Bug|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Pavel Zhukov 2019-07-09 07:23:11 UTC
Description of problem: gdb segfaults with core if working directory was deleted Version-Release number of selected component (if applicable): gdb-8.3-6.fc30.x86_64 How reproducible: 100% Steps to Reproduce: 1. mkdir /tmp/test 2. cd /tmp/test 3. rm -rf /tmp/test 4. gdb echo Actual results: Segmentation fault (core dumped) Expected results: No core Additional info:
Comment 1 Sergio Durigan Junior 2019-07-10 23:50:10 UTC
Patch submitted: https://sourceware.org/ml/gdb-patches/2019-07/msg00289.html
Comment 2 Ben Cotton 2019-10-31 19:04:02 UTC
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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.
Comment 3 Ben Cotton 2019-11-27 23:00:26 UTC
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.
Comment 4 Sergio Durigan Junior 2019-12-16 20:24:04 UTC
Reopening for F30.
Comment 5 Sergio Durigan Junior 2020-02-04 21:32:12 UTC
I am pushing a fix for this problem, but only for F31 GDB. Let me know if you need the fix for F30, and I'll be happy to clone this bug and backport the patch.
Comment 6 Fedora Update System 2020-02-04 21:57:26 UTC
FEDORA-2020-c97e9ccfdd has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c97e9ccfdd
Comment 7 Fedora Update System 2020-02-05 01:25:19 UTC
gdb-220.127.116.1190824-28.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c97e9ccfdd
Comment 8 Fedora Update System 2020-02-07 01:51:02 UTC
gdb-18.104.22.16890824-28.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.