Description of problem: When I'm shutting down Xorg server - I'm getting weird coredump, which is even confusing gdb (which then generates another coredump) #0 0x0000000000000030 in ?? () Missing separate debuginfos, use: debuginfo-install audit-libs-2.2.1-1.fc18.x86_64 libXau-1.0.6-3.fc17.x86_64 libXdmcp-1.1.1-1.fc17.x86_64 libfontenc-1.1.1-1.fc18.x86_64 libpciaccess-0.13.1-1.fc18.x86_64 libselinux-2.1.11-1.fc18.x86_64 openssl-libs-1.0.1c-1.fc18.x86_64 zlib-1.2.7-3.fc18.x86_64 (gdb) bt #0 0x0000000000000030 in ?? () #1 0x0000000000428d59 in FreeCursor (value=0x22cb800, cid=cid@entry=0) at cursor.c:122 #2 0x00000000004b755d in xf86_cursors_fini ( ../../gdb/dwarf2read.c:8284: internal-error: read_call_site_scope: Assertion `offset.sect_off >= cu->header.offset.sect_off' failed. A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n) So it seems like something in shutdown path is freeing something in bad way. Version-Release number of selected component (if applicable): xorg-x11-server-Xorg-1.12.3-1.fc18.x86_64 gdb-7.4.50.20120703-12.fc18.x86_64 How reproducible: Steps to Reproduce: 1. startx 2. use X session for a while (firefox, thunderbird) 3. kill Xsession Actual results: Expected results: Additional info: I think last 'reasonable' usable version was: xorg-x11-server-1.12.2-3.fc18 Newer packages (or its debug info) are confusing gdb)
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
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.