Description of problem: when using the Eclipse CDT with GDB to debug an overly large C++ application (LibreOffice) occasionally the following exception is printed: Exception in thread "MI TX Thread" java.lang.NullPointerException at org.eclipse.cdt.dsf.mi.service.command.commands.MICommand$MIStandardParameterAdjustable.getAdjustedValue(MICommand.java:331) at org.eclipse.cdt.dsf.mi.service.command.commands.MICommand.parametersToString(MICommand.java:239) at org.eclipse.cdt.dsf.mi.service.command.commands.MICommand.constructCommand(MICommand.java:172) at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$TxThread.run(AbstractMIControl.java:650) when this happens Eclipse CDT somehow gets confused and disables all of the debugging UI; only thing that still works then is the "Terminate" button to detach from the inferior. in case it matters, the inferior has some custom GDB python helpers to print various data types that are evidently used to display stuff in Eclipse CDT as well. Version-Release number of selected component (if applicable): eclipse-cdt-8.1.0-1.fc17.x86_64 How reproducible: had this happen about 3 times yesterday, but haven't figured out how to reproduce it... when it happens it's usually after debugging for an hour or two. Actual results: Eclipse CDT becomes mostly non-functional; only thing that works is "Terminate" & then re-attach which is very annoying Expected results: perhaps it would be possible to handle this error in a better way to at least be able to continue using Eclipse CDT with the inferior. Additional info: installed relevant packages: gdb-7.4.50.20120120-52.fc17.x86_64 eclipse-platform-4.2.1-2.fc17.x86_64 eclipse-birt-chart-4.2.1-1.fc17.noarch eclipse-equinox-osgi-4.2.1-2.fc17.x86_64 eclipse-linuxprofilingframework-1.0.0-2.fc17.x86_64 eclipse-gef-3.8.1-3.fc17.noarch eclipse-emf-core-2.8.1-2.fc17.x86_64 icu4j-eclipse-4.4.2.2-11.fc17.noarch eclipse-cdt-8.1.0-1.fc17.x86_64 eclipse-rse-3.4-1.fc17.noarch eclipse-emf-2.8.1-1.fc17.noarch eclipse-valgrind-1.0.0-1.fc17.x86_64 eclipse-swt-4.2.1-2.fc17.x86_64 eclipse-rcp-4.2.1-2.fc17.x86_64 eclipse-dtp-1.10.1-1.fc17.noarch
Any chance you could try the same scenario using the CPP EPP from Eclipse.org? That will eliminate whether this is an upstream CDT bug vs a Fedora one. You can find the Juno SR1 C/C++ IDE from: http://www.eclipse.org/downloads/packages/ You can just untar the file locally and start the eclipse executable which is found under the eclipse sub-directory. It will not affect your current Fedora eclipse or eclipse-cdt installations. You might want to use a separate workspace to reproduce the problem. If it also occurs on the downloaded version, I'll open an upstream report. Without a reliable way of reproducing, it might be difficult to pin-point but the issue might ring a bell with the CDT debug team. Another thing you might try is to use another version of gdb (either prior to the latest version or latest version if you are not using it). It might be a problem in what the MI interface is returning to CDT. This won't solve how the error is handled, but it might get you around the problem or confirm it has been solved on the gdb side.
Michael, could you please respond to the previous comment. I will post upstream to see if any of the debugger maintainers have seen the issue.
Michael, after posting to the CDT developer list, it was suggested that the next time this occurs, please capture the last 50 or so lines of the gdb trace console and post them here. That may help pinpoint what has occurred. Details on locating the trace can be found here: http://wiki.eclipse.org/CDT/User/FAQ#I.27ve_been_asked_for_.27gdb_traces.27.2C_where_can_I_find_them.3F
Created attachment 680220 [details] eclipse gdb trace sorry i've been on vacation and haven't paid attention :) now i've got a gdb trace from yesterday (still on the Fedora 17 packages), which i'll attach shortly; likely i'll upgrade to F18 in any case soon and see if there's any improvement there.
Created attachment 689986 [details] eclipse gdb trace on Fedora 18 just had the problem on Fedora 18, with the same stack as in the Description printed. gdb-7.5.1-32.fc18.x86_64 eclipse-cdt-8.1.1-1.fc18.x86_64
Created attachment 717308 [details] eclipse gdb trace upstream juno sr2 just had the same problem with an upstream Eclipse JunoSR2 binary gdb-7.5.1-37.fc18.x86_64 eclipse-cpp-juno-SR2-linux-gtk-x86_64.tar.gz
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.
had the same problem earlier this week on Fedora 19 eclipse-cdt-8.2.0-1.fc19.x86_64 gdb-7.6-34.fc19.x86_64 Exception in thread "MI TX Thread" java.lang.NullPointerException at org.eclipse.cdt.dsf.mi.service.command.commands.MICommand$MIStandardParameterAdjustable.getAdjustedValue(MICommand.java:331) at org.eclipse.cdt.dsf.mi.service.command.commands.MICommand.parametersToString(MICommand.java:239) at org.eclipse.cdt.dsf.mi.service.command.commands.MICommand.constructCommand(MICommand.java:172) at org.eclipse.cdt.dsf.mi.service.command.AbstractMIControl$TxThread.run(AbstractMIControl.java:652)
Michael, still no reproduce steps you can provide ?
(In reply to Alexander Kurtakov from comment #10) > Michael, still no reproduce steps you can provide ? sadly not, and the problem seems to happen less often for me now; is there some way to get more logging from eclipse or gdb than the attached trace-logs?
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.