| AW: AW: [photran] New Photran build available |
|
Hi Jeff, here are the first 13 (hence all) lines under the exception from the
.log file: at
bz.over.vpg.cdtdb.org.eclipse.cdt.internal.core.pdom.db.Chunk.getInt(Chunk.java:92) at
bz.over.vpg.cdtdb.org.eclipse.cdt.internal.core.pdom.db.Database.free(Database.java:363) at bz.over.vpg.db.cdt.InternalCDTDB$Annotations.deleteAllAnnotationsFor(InternalCDTDB.java:1138) at
bz.over.vpg.db.cdt.CDTDB.deleteAllEdgesAndAnnotationsFor(CDTDB.java:162) at
bz.over.vpg.db.caching.CachingDB.deleteAllEdgesAndAnnotationsFor(CachingDB.java:144) at org.eclipse.photran.core.vpg.PhotranVPGDB.deleteAllEdgesAndAnnotationsFor(PhotranVPGDB.java:108) at bz.over.vpg.VPG.computeEdgesAndAnnotations(VPG.java:177) at bz.over.vpg.VPG.acquireTransientAST(VPG.java:123) at
bz.over.vpg.VPG.forceRecomputationOfEdgesAndAnnotations(VPG.java:211) at bz.over.vpg.eclipse.EclipseVPG$VPGResourceDeltaVisitor.index(EclipseVPG.java:380) at
bz.over.vpg.eclipse.EclipseVPG$VPGResourceDeltaJob.runInWorkspace(EclipseVPG.java:278) at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) I also tried your suggestion, to clear and refresh the VPG Database. And
this fixes the problem – at least currently. Thanks for this good approach! Best regards Stefan -----Ursprüngliche Nachricht----- Hi Stefan, Could you please copy the first 5-10 lines under the "ArrayIndexOutOfBoundsException" from the .log file and post
that? Also, try clicking on Refactor > (Debugging) > Clear VPG Database
and then Refactor > (Debugging) > Refresh VPG Database. There is a situation we haven't identified yet when the indexer database gets corrupted, and that causes errors like this to occur. Thanks. Jeff Stefan Krieger wrote: > Hello, > > I am working with Photran (newest version) on a Linux Ubuntu
system (Ubuntu > 9.04, Eclipse 3.4.2, CDT 5.0.2, SUN Java 1.6.0_13). Until today
everything > worked fine and I was very happy with Photran - it's fantastic! > > But now, every time, I enter a sign (even just a simple space), a
window > pops up with the title "Multiple problems have
occurred". It tells me that > "An internal error occurred during: "Photran
indexer"." In the Details it > says only -4 as an additional information. > > When I open the log file (workspace, -> .metadata, -> .log)
I can see > corresponding entries and it seems to be an > java.lang.ArrayIndexOutOfBoundsException, which is responsible for
the > error. > > If I turn out the Fortran Analysis/Refactoring in the Project
Properties, > everything works fine. > > I do not know, whether this error is already known and perhaps
already > entered in BugZilla. Therefore count my mail as an information -
not as an > instruction... ;-) > > Best regards > Stefan Krieger > > --- > working with Photran at the Ruhr-University Bochum in > > > > > -----Ursprüngliche Nachricht----- > Von: photran-bounces@xxxxxxxxxxx
[mailto:photran-bounces@xxxxxxxxxxx] Im > Auftrag von Jeffrey Overbey > Gesendet: Sonntag, 24. Mai 2009 01:07 > An: Photran@xxxxxxxxxxx:A Fortran Plug-in for Eclipse > Betreff: [photran] New Photran build available > > A new build (I200905152006) of Photran is available from the wiki:
> http://wiki.eclipse.org/PTP/builds/photran/4.0 > > This fixes the "Notification" indexer error (due to
ENTRY statements) as > well as a NullPointerException, and I *think* the gfortran error
parser > problems should be resolved as well (please post if they are
not). Of > course, there are more bug fixes in progress, notably
parser/indexer > problems... > > Jeff > _______________________________________________ > photran mailing list > photran@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/photran > > _______________________________________________ > photran mailing list > photran@xxxxxxxxxxx > https://dev.eclipse.org/mailman/listinfo/photran > > _______________________________________________ photran mailing list photran@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/photran |