Wednesday, September 14, 2011
gdb: unknown target exception
Q: I launched a debug configuration in Optima 2.4 and got this error:
gdb: unknown target exception 0xc0000135 at 0x7c9666c6
You can't do that without a process to debug.
I have followed everything in the Optima UG docs section 6 exactly as written. Why does gdb think there is isn't a program?
A: Sometimes when you create a new debug/run config there is weirdness with launching it right away. Close and restart the eclipse tool and it should launch correctly afterward.
Q: A similar problem with Optima 2.5 - looking in the debug configuration and supposed to see a special OSE tab to configure OSE kernel-awareness, but the tab isn't there.
A: Custom configuration tabs (such as the new custom tab in the Optima 2.5 release) might have the same problem - eclipse may get confused the first time you try to access it via the debug config, or when trying to access it within a project created in an earlier eclipse/Optima release. Try switching to a different workspace and restarting Optima. The OSE tab should now appear when entering the debug configuration menu.
gdb: unknown target exception 0xc0000135 at 0x7c9666c6
You can't do that without a process to debug.
I have followed everything in the Optima UG docs section 6 exactly as written. Why does gdb think there is isn't a program?
A: Sometimes when you create a new debug/run config there is weirdness with launching it right away. Close and restart the eclipse tool and it should launch correctly afterward.
Q: A similar problem with Optima 2.5 - looking in the debug configuration and supposed to see a special OSE tab to configure OSE kernel-awareness, but the tab isn't there.
A: Custom configuration tabs (such as the new custom tab in the Optima 2.5 release) might have the same problem - eclipse may get confused the first time you try to access it via the debug config, or when trying to access it within a project created in an earlier eclipse/Optima release. Try switching to a different workspace and restarting Optima. The OSE tab should now appear when entering the debug configuration menu.
Labels: debugger, Optima, optima2.4, optima2.5
free invisible web counter
