Description of problem: I got a coredump which confuses gdb in way that when I open it (gdb -c coredump), gdb correctly tells me where the crash occurred: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007f283a4edf93 in invoke_handler (binding=0x54eeb00, event=0x7063a70, window=0x0, handler=0x888fe60, screen=0x16b96c0, display=0x34ccc10) at core/keybindings.c:1737 1737 (* handler->func) (display, screen, but output of the command 'bt' starts with these lines: #0 0x00007f283a4edf93 in process_event (binding=0x54eeb00, event=0x7063a70, window=0x0, handler=0x888fe60, screen=0x16b96c0 [MetaScreen], display=0x34ccc10 [MetaDisplay]) at core/keybindings.c:1737 #1 0x00007f283a4edf93 in process_event (display=display@entry=0x34ccc10 [MetaDisplay], screen=screen@entry=0x16b96c0 [MetaScreen], window=window@entry=0x0, event=event@entry=0x7063a70) at core/keybindings.c:1791 #2 0x00007f283a4ef556 in meta_keybindings_process_event (event=0x7063a70, window=0x0, screen=0x16b96c0 [MetaScreen], display=0x34ccc10 [MetaDisplay]) at core/keybindings.c:1762 #3 0x00007f283a4ef556 in meta_keybindings_process_event (event=0x7063a70, window=0x0, display=0x34ccc10 [MetaDisplay]) at core/keybindings.c:2031 #4 0x00007f283a4ef556 in meta_keybindings_process_event (display=display@entry=0x34ccc10 [MetaDisplay], window=window@entry=0x0, event=event@entry=0x7063a70) at core/keybindings.c:2064 #5 0x00007f283a4e9259 in event_callback (event=0x7063a70, display=0x34ccc10 [MetaDisplay]) at core/events.c:249 #6 0x00007f283a4e9259 in event_callback (event=0x7063a70, data=0x34ccc10) at core/events.c:327 The name of the frame #0 in the output of the command 'bt' has an invalid name and address. Version-Release number of selected component (if applicable): gdb-7.8.2-38.fc21.x86_64 How reproducible: Always with that particular coredump file. Actual results: The top frame of the crash thread does not equal the crash frame. Expected results: The top frame of the crash thread equals the crash frame. Additional info: $ eu-stack -v --core=coredump PID 11113 - core TID 11113: #0 0x00007f283a4edf93 invoke_handler - libmutter.so.0 core/keybindings.c:1737 #1 0x00007f283a4edf93 process_event - libmutter.so.0 core/keybindings.c:1791 #2 0x00007f283a4ef556 - 1 process_event - libmutter.so.0 core/keybindings.c:1762 #3 0x00007f283a4ef556 - 1 process_key_event - libmutter.so.0 core/keybindings.c:2031 #4 0x00007f283a4ef556 - 1 meta_keybindings_process_event - libmutter.so.0 core/keybindings.c:2064 #5 0x00007f283a4e9259 - 1 meta_display_handle_event - libmutter.so.0 core/events.c:249 #6 0x00007f283a4e9259 - 1 event_callback - libmutter.so.0 core/events.c:327 ....
Frame #0 is apparently inlined info frame #1. Which function to display then is a topic for Bug 1228549 but here we assume the inlined function should be displayed. Additionally frame #0/#1 has a Python frame filter applied. And Python frame filters: (a) Python frame filters apply only to 'backtrace' cmd but not 'frame' cmd. 'core-file' command calls the 'frame' command at its end. https://sourceware.org/bugzilla/show_bug.cgi?id=18567 filed with no patch (b) Python frame filters incorrectly display the linkage function (frame #1 in this case) and not the inlined function (frame #0). A draft fix is here but it has output regression: https://sourceware.org/bugzilla/show_bug.cgi?id=18565 draft fix
This message is a reminder that Fedora 21 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 21. 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 '21'. 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 21 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.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.