Quote:
Originally Posted by jhersh
So you don't ever get the debugger to stop when the exception occurs? It sounds like you are attaching the debugger in response to a crash. Try attaching the debugger to the running python interpreter before you do whatever instigates the crash or start the python interpreter using the debugger. When the exception occurs, you should be able to open the stack view. That would be the first helpful piece of information in tracking down the issue.
|
this is the stack view I got:
Quote:
java.io.FileNotFoundException
at org.eclipse.help.internal.context.ContextFileProvi der.loadContexts(ContextFileProvider.java:235)
at org.eclipse.help.internal.context.ContextFileProvi der.getContexts(ContextFileProvider.java:181)
at org.eclipse.help.internal.context.ContextFileProvi der.getPluginContexts(ContextFileProvider.java:158 )
at org.eclipse.help.internal.context.ContextFileProvi der.getContext(ContextFileProvider.java:83)
at org.eclipse.help.internal.context.ContextManager.g etContext(ContextManager.java:79)
at org.eclipse.help.HelpSystem.getContext(HelpSystem. java:49)
at com.windriver.ide.internal.apidoc.WRAPIHelpProvide r.getFunctionInfo(WRAPIHelpProvider.java:110)
at org.eclipse.cdt.internal.ui.text.CHelpSettings.get FunctionInfo(CHelpSettings.java:121)
at org.eclipse.cdt.internal.ui.CHelpProviderManager.g etFunctionInfo(CHelpProviderManager.java:163)
at org.eclipse.cdt.internal.ui.text.c.hover.CDocHover .getHoverInfo(CDocHover.java:73)
at org.eclipse.cdt.internal.ui.text.c.hover.BestMatch Hover.getHoverInfo(BestMatchHover.java:100)
at org.eclipse.cdt.internal.ui.text.c.hover.CEditorTe xtHoverProxy.getHoverInfo(CEditorTextHoverProxy.ja va:64)
at org.eclipse.jface.text.TextViewerHoverManager$4.ru n(TextViewerHoverManager.java:165)
|
and the error messege was:
Code:
Error reading context-sensitive help file /"com.windriver.ide.doc.wr_vx_simulator_6.3/wr_workbench_diagnostics_programmers_guide_1.1/html/contexts.xml" (skipping file)