Hi,
I'm currently using Code Warrior on windows 7 - 64 bits . Previously, everything worked fine. Two days ago, I started having problems while debugging. Find attached a screen shot of the error.
Thank you for your help.
Regards,
Kamelia Bakiri
Solved! Go to Solution.
Hello Kamelia
We have received an explanation from the CodeWarrior debugger development team in regards of the CORBA error:
Q:What is causing the CORBA error to happen? How to avoid this or fix it?
A: The CORBA error appears when DE.exe crashes, thus CW looses connection to the debugger unexpectedly.
Workaround: In <CWInstallPath>/eclipse/cwide.ini, add -Dcw.junitTesting=true at the end of the file and relaunch CW. Now, if DE.exe crashes for whatever reason, the CORBA error won't be displayed and DE will be automatically relaunched on the next CW operation that needs the debugger (e.g launching a new debug session).
Note that, as a side-effect for this workaround, Target Task Framework (TTF) errors won't be displayed anymore; you will need to check the 'Problems view' in Console to see such errors.
Hope this helps!
Best Regards
Fiona Kuang
Technical Information & Commercial Support
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Mark Correct button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hello Kamelia
We have received an explanation from the CodeWarrior debugger development team in regards of the CORBA error:
Q:What is causing the CORBA error to happen? How to avoid this or fix it?
A: The CORBA error appears when DE.exe crashes, thus CW looses connection to the debugger unexpectedly.
Workaround: In <CWInstallPath>/eclipse/cwide.ini, add -Dcw.junitTesting=true at the end of the file and relaunch CW. Now, if DE.exe crashes for whatever reason, the CORBA error won't be displayed and DE will be automatically relaunched on the next CW operation that needs the debugger (e.g launching a new debug session).
Note that, as a side-effect for this workaround, Target Task Framework (TTF) errors won't be displayed anymore; you will need to check the 'Problems view' in Console to see such errors.
Hope this helps!
Best Regards
Fiona Kuang
Technical Information & Commercial Support
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Mark Correct button. Thank you!
-----------------------------------------------------------------------------------------------------------------------