Skip to main content



      Home
Home » Eclipse Projects » Eclipse Platform » Debug stack is blank, .log has StringIndexOutOfBoundsException
Debug stack is blank, .log has StringIndexOutOfBoundsException [message #77953] Wed, 18 June 2003 14:02 Go to next message
Eclipse UserFriend
Originally posted by: magellan94.hotmail.com

Has anybody seen this problem? I recently upgraded from 2.1 to 3.0 M1, and I
am seeing an exception in the debug perspective. As soon as execution hits a
breakpoint, the debugger becomes active and Eclipse tries to update the
debug view. Suddenly, a dialog appears to tell me that an error has occurred
and that I should check the metadata/.log file for error messages. The .log
file shows a stack trace for a java.lang.StringIndexOutOfBoundsException
(see below for the entire stack trace.) After dismissing the dialog, the
stack view in the debugger his blank lines where the stack frames should be.
Closing and reopening the debug view clears the problem, but it crops up
again the next time a breakpoint is hit. Is this a known bug? Does anybody
know the cause? If nobody has seen it, I'll log the bug.

Here's the system information output in my eclipse log:
java.version=1.4.2-beta
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
Command-line arguments: -os win32 -ws win32 -arch x86 -data -install
file:E:/java/eclipse/current/eclipse/

Thanks, Dave

[stack trace from .log]
!MESSAGE Unhandled exception caught in event loop.
!ENTRY org.eclipse.ui 4 0 Jun 09, 2003 17:43:17.420
!MESSAGE String index out of range: 0
!STACK 0
java.lang.StringIndexOutOfBoundsException: String index out of range: 0
at java.lang.StringBuffer.charAt(StringBuffer.java:274)
at
org.eclipse.jdi.internal.SourceDebugExtensionParser.getNonAs teriskString(Sou
rceDebugExtensionParser.java:514)
at
org.eclipse.jdi.internal.SourceDebugExtensionParser.parseFil eInfo(SourceDebu
gExtensionParser.java:405)
at
org.eclipse.jdi.internal.SourceDebugExtensionParser.parseFil eSection(SourceD
ebugExtensionParser.java:378)
at
org.eclipse.jdi.internal.SourceDebugExtensionParser.parseStr atumSection(Sour
ceDebugExtensionParser.java:338)
at
org.eclipse.jdi.internal.SourceDebugExtensionParser.parseSec tions(SourceDebu
gExtensionParser.java:310)
at
org.eclipse.jdi.internal.SourceDebugExtensionParser.parseSma p(SourceDebugExt
ensionParser.java:278)
at
org.eclipse.jdi.internal.SourceDebugExtensionParser.parse(So urceDebugExtensi
onParser.java:260)
at
org.eclipse.jdi.internal.ReferenceTypeImpl.getSourceDebugExt ension(Reference
TypeImpl.java:1516)
at
org.eclipse.jdi.internal.ReferenceTypeImpl.isSourceDebugExte nsionAvailable(R
eferenceTypeImpl.java:1562)
at
org.eclipse.jdi.internal.ReferenceTypeImpl.getStratum(Refere nceTypeImpl.java
:1478)
at
org.eclipse.jdi.internal.ReferenceTypeImpl.lineNumber(Refere nceTypeImpl.java
:1712)
at org.eclipse.jdi.internal.LocationImpl.lineNumber(LocationImp l.java:163)
at org.eclipse.jdi.internal.LocationImpl.lineNumber(LocationImp l.java:109)
at
org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getL ineNumber(JDISta
ckFrame.java:330)
at
org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getSt ackFrameText(JDI
ModelPresentation.java:1388)
at
org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getTe xt(JDIModelPrese
ntation.java:201)
at
org.eclipse.debug.internal.ui.LazyModelPresentation.getText( LazyModelPresent
ation.java:74)
at
org.eclipse.debug.internal.ui.DelegatingModelPresentation.ge tText(Delegating
ModelPresentation.java:127)
at
org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.append(C
opyToClipboardActionDelegate.java:86)
at
org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.append(C
opyToClipboardActionDelegate.java:93)
at
org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.doAction
(CopyToClipboardActionDelegate.java:74)
at
org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate$1.run(Co
pyToClipboardActionDelegate.java:127)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
at
org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.run(Copy
ToClipboardActionDelegate.java:123)
at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:263)
at
org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(Action
ContributionItem.java:542)
at
org.eclipse.jface.action.ActionContributionItem.access$4(Act ionContributionI
tem.java:496)
at
org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContribu
tionItem.java:468)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :81)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:848)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2034)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :1741)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1399)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1382)
at
org.eclipse.core.internal.boot.InternalBootLoader.run(Intern alBootLoader.jav
a:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
..java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)
Re: Debug stack is blank, .log has StringIndexOutOfBoundsException [message #80766 is a reply to message #77953] Mon, 23 June 2003 11:55 Go to previous message
Eclipse UserFriend
Originally posted by: John_Arthorne.oti.com_

You should just enter the bug report. If it is a duplicate, they can
easily close it.
--


Dave Smith wrote:
> Has anybody seen this problem? I recently upgraded from 2.1 to 3.0 M1, and I
> am seeing an exception in the debug perspective. As soon as execution hits a
> breakpoint, the debugger becomes active and Eclipse tries to update the
> debug view. Suddenly, a dialog appears to tell me that an error has occurred
> and that I should check the metadata/.log file for error messages. The .log
> file shows a stack trace for a java.lang.StringIndexOutOfBoundsException
> (see below for the entire stack trace.) After dismissing the dialog, the
> stack view in the debugger his blank lines where the stack frames should be.
> Closing and reopening the debug view clears the problem, but it crops up
> again the next time a breakpoint is hit. Is this a known bug? Does anybody
> know the cause? If nobody has seen it, I'll log the bug.
>
> Here's the system information output in my eclipse log:
> java.version=1.4.2-beta
> java.vendor=Sun Microsystems Inc.
> BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_GB
> Command-line arguments: -os win32 -ws win32 -arch x86 -data -install
> file:E:/java/eclipse/current/eclipse/
>
> Thanks, Dave
>
> [stack trace from .log]
> !MESSAGE Unhandled exception caught in event loop.
> !ENTRY org.eclipse.ui 4 0 Jun 09, 2003 17:43:17.420
> !MESSAGE String index out of range: 0
> !STACK 0
> java.lang.StringIndexOutOfBoundsException: String index out of range: 0
> at java.lang.StringBuffer.charAt(StringBuffer.java:274)
> at
> org.eclipse.jdi.internal.SourceDebugExtensionParser.getNonAs teriskString(Sou
> rceDebugExtensionParser.java:514)
> at
> org.eclipse.jdi.internal.SourceDebugExtensionParser.parseFil eInfo(SourceDebu
> gExtensionParser.java:405)
> at
> org.eclipse.jdi.internal.SourceDebugExtensionParser.parseFil eSection(SourceD
> ebugExtensionParser.java:378)
> at
> org.eclipse.jdi.internal.SourceDebugExtensionParser.parseStr atumSection(Sour
> ceDebugExtensionParser.java:338)
> at
> org.eclipse.jdi.internal.SourceDebugExtensionParser.parseSec tions(SourceDebu
> gExtensionParser.java:310)
> at
> org.eclipse.jdi.internal.SourceDebugExtensionParser.parseSma p(SourceDebugExt
> ensionParser.java:278)
> at
> org.eclipse.jdi.internal.SourceDebugExtensionParser.parse(So urceDebugExtensi
> onParser.java:260)
> at
> org.eclipse.jdi.internal.ReferenceTypeImpl.getSourceDebugExt ension(Reference
> TypeImpl.java:1516)
> at
> org.eclipse.jdi.internal.ReferenceTypeImpl.isSourceDebugExte nsionAvailable(R
> eferenceTypeImpl.java:1562)
> at
> org.eclipse.jdi.internal.ReferenceTypeImpl.getStratum(Refere nceTypeImpl.java
> :1478)
> at
> org.eclipse.jdi.internal.ReferenceTypeImpl.lineNumber(Refere nceTypeImpl.java
> :1712)
> at org.eclipse.jdi.internal.LocationImpl.lineNumber(LocationImp l.java:163)
> at org.eclipse.jdi.internal.LocationImpl.lineNumber(LocationImp l.java:109)
> at
> org.eclipse.jdt.internal.debug.core.model.JDIStackFrame.getL ineNumber(JDISta
> ckFrame.java:330)
> at
> org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getSt ackFrameText(JDI
> ModelPresentation.java:1388)
> at
> org.eclipse.jdt.internal.debug.ui.JDIModelPresentation.getTe xt(JDIModelPrese
> ntation.java:201)
> at
> org.eclipse.debug.internal.ui.LazyModelPresentation.getText( LazyModelPresent
> ation.java:74)
> at
> org.eclipse.debug.internal.ui.DelegatingModelPresentation.ge tText(Delegating
> ModelPresentation.java:127)
> at
> org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.append(C
> opyToClipboardActionDelegate.java:86)
> at
> org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.append(C
> opyToClipboardActionDelegate.java:93)
> at
> org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.doAction
> (CopyToClipboardActionDelegate.java:74)
> at
> org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate$1.run(Co
> pyToClipboardActionDelegate.java:127)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator .java:69)
> at
> org.eclipse.debug.internal.ui.actions.CopyToClipboardActionD elegate.run(Copy
> ToClipboardActionDelegate.java:123)
> at org.eclipse.ui.internal.PluginAction.runWithEvent(PluginActi on.java:263)
> at
> org.eclipse.jface.action.ActionContributionItem.handleWidget Selection(Action
> ContributionItem.java:542)
> at
> org.eclipse.jface.action.ActionContributionItem.access$4(Act ionContributionI
> tem.java:496)
> at
> org.eclipse.jface.action.ActionContributionItem$6.handleEven t(ActionContribu
> tionItem.java:468)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java :81)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:848)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.ja va:2034)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java :1741)
> at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.jav a:1399)
> at org.eclipse.ui.internal.Workbench.run(Workbench.java:1382)
> at
> org.eclipse.core.internal.boot.InternalBootLoader.run(Intern alBootLoader.jav
> a:858)
> at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:39
> )
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl
> .java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
> at org.eclipse.core.launcher.Main.run(Main.java:747)
> at org.eclipse.core.launcher.Main.main(Main.java:583)
>
>
Previous Topic:CVS Compare of ASCII file give _binary_ compare error
Next Topic:CVS integration build I20030618
Goto Forum:
  


Current Time: Mon Jul 14 07:57:46 EDT 2025

Powered by FUDForum. Page generated in 0.07426 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top