Created attachment 381831 [details] GDB workaround of the Eclipse bug. Description of problem: FSF gdb-7.0+ supports stepping into inlined functions. Which is no CPU step at all, only more frames get reported without any change of real PC. In this case "-exec-step 1" generates immediate async "*stopped" record together with "^done" record. Eclipse ignores such operation unless it sees "^running" as a result. While it can be workarounded in GDB I believe Eclipse should be fixed instead. Version-Release number of selected component (if applicable): eclipse-cdt-6.0.0-10.fc12.x86_64 eclipse-emf-2.5.0-4.fc12.noarch eclipse-platform-3.5.1-21.fc12.x86_64 eclipse-rcp-3.5.1-21.fc12.x86_64 eclipse-rse-3.1-2.fc12.noarch eclipse-swt-3.5.1-21.fc12.x86_64 How reproducible: Always. Steps to Reproduce: source: ------------------------------------------------------------------------------- static __attribute__ ((__always_inline__)) void func (void) { volatile int i = 1; i = i; } int main (void) { volatile int j = 2; func (); return 0; } ------------------------------------------------------------------------------- Debug as -> Local C/C++ Application. It stops at "volatile int j = 2;" - screenshot 0. F5 - Step Into It stops at "func ();" - screenshot 1. F5 - Step Into Actual results: It stays stopped at "func();" - screenshot 2bad. Expected results: It stops at "volatile int i = 1;" - screenshot 2good. F5 - Step Into It stops at "i = 1;" - screenshot 3. Additional info: bad case - the current unpatched behavior: 1414-exec-step 1 -> (gdb) *stopped,frame={addr="0x0000000000400492",func="func",args=[],file="../inlineskip.c",fullname="/home/jkratoch/workspace/inlineskip/inlineskip.c",line="4"},thread-id="1",stopped-threads="all" 1414^done (gdb) good case - with workaround in GDB: 1478-exec-step 1 -> (gdb) 1478^running *running,thread-id="1" (gdb) *stopped,frame={addr="0x0000000000400492",func="func",args=[],file="../inlineskip.c",fullname="/home/jkratoch/workspace/inlineskip/inlineskip.c",line="4"},thread-id="1",stopped-threads="all" (gdb) This problem is targeted at -O2 -g debugging and there are more cases to be introduced in GDB with this behavior (of no real PC change). Currently it happens also for stepping-out of inlined functions and it will happen even for first step after stepping-out of normal functions.
Created attachment 381832 [details] Eclipse screenshots + GDB MI input/output.
MI doc update suggests how to fix Eclipse: http://sourceware.org/ml/gdb-patches/2010-02/msg00319.html @item "^running" @findex ^running This result record is equivalent to @samp{^done}. Historically, it was output instead of @samp{^done} if the command has resumed the target. This behaviour is maintained for backward compatibility, but all frontends should treat @samp{^done} and @samp{^running} identically and rely on the @samp{*running} output record to determine which threads are resumed.
I have opened a bug upstream on the CDT CDI debug for this issue. DSF gets the step into the inline function correct, but it hangs there and the step/next/etc.. buttons are disabled.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
eclipse-cdt-6.0.2-5.fc13.x86_64 gdb-7.1-34.fc13.x86_64
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. 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 '13'. 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 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Not reverified but I haven't heard about a fix.
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.