Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 334280

Summary:	BadLocationException logged by ApiAnalysisBuilder
Product:	[Eclipse Project] PDE	Reporter:	James Blackburn <jamesblackburn+eclipse>
Component:	API Tools	Assignee:	PDE API Tools Inbox <pde-apitools-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	curtis.windatt.public
Version:	3.7
Target Milestone:	---
Hardware:	PC
OS:	Linux-GTK
See Also:	https://bugs.eclipse.org/bugs/show_bug.cgi?id=532557
Whiteboard:	stalebug

Description James Blackburn

2011-01-13 11:37:02 EST

I've got a whole bunch of BadLocationExceptions logged by the API tooling:

Error logged from API Tools Core: 
org.eclipse.jface.text.BadLocationException
	at org.eclipse.jface.text.ListLineTracker.getLineNumberOfOffset(ListLineTracker.java:140)
	at org.eclipse.jface.text.AbstractLineTracker.getLineNumberOfOffset(AbstractLineTracker.java:161)
	at org.eclipse.jface.text.AbstractDocument.getLineOfOffset(AbstractDocument.java:915)
	at org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:394)
	at org.eclipse.pde.api.tools.internal.builder.AbstractProblemDetector.createProblem(AbstractProblemDetector.java:180)
	at org.eclipse.pde.api.tools.internal.builder.AbstractProblemDetector.createProblems(AbstractProblemDetector.java:421)
	at org.eclipse.pde.api.tools.internal.builder.ReferenceAnalyzer.analyze(ReferenceAnalyzer.java:263)
	at org.eclipse.pde.api.tools.internal.builder.BaseApiAnalyzer.checkApiUsage(BaseApiAnalyzer.java:1098)
	at org.eclipse.pde.api.tools.internal.builder.BaseApiAnalyzer.analyzeComponent(BaseApiAnalyzer.java:271)
	at org.eclipse.pde.api.tools.internal.builder.IncrementalApiBuilder.build(IncrementalApiBuilder.java:272)
	at org.eclipse.pde.api.tools.internal.builder.IncrementalApiBuilder.build(IncrementalApiBuilder.java:230)
	at org.eclipse.pde.api.tools.internal.builder.ApiAnalysisBuilder.build(ApiAnalysisBuilder.java:357)
	at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:713)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:188)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:225)
	at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:278)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:281)
	at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:337)
	at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:360)
	at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:143)
	at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

Comment 1 Curtis Windatt

2011-01-19 17:44:26 EST

Can you provide steps to reproduce?

Comment 2 James Blackburn

2011-01-20 04:31:06 EST

I'm not sure.  Perhaps I was editing the file concurrently?

I notice that:

org.eclipse.core.internal.filebuffers.SynchronizableDocument.getLineOfOffset(SynchronizableDocument.java:394)

isn't synchronized, though the API does allow synchronization with a lock object. Without deeper knowledge of how filebuffers are shared(?), I'm just stabbing in the dark here...

Comment 3 Eclipse Genie

2021-01-25 04:33:59 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.

Comment 4 Eclipse Genie

2023-01-16 03:15:36 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.