This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 127307 - Error elements produced by source parser
Summary: Error elements produced by source parser
Status: RESOLVED WONTFIX
Alias: None
Product: java
Classification: Unclassified
Component: Source (show other bugs)
Version: 6.x
Hardware: All All
: P3 blocker (vote)
Assignee: Rastislav Komara
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-02-13 14:47 UTC by Martin Entlicher
Modified: 2009-11-02 10:57 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
php.parser project. (44.60 KB, application/octet-stream)
2008-02-13 14:47 UTC, Martin Entlicher 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Entlicher 2008-02-13 14:47:07 UTC 
It might be caused by a labeled block, not sure, but there are error elements produced by the javac parser.
To reproduce, unzip the attached php.parser.zip into HG main, open as a project in NetBeans IDE and see PHP5Scanner.java.

When on line 596, zzCurrentPosL is resolved as com.sun.tools.javac.code.Symbol$VarSymbol element. That is O.K. and expected.
But when on line 602, zzCurrentPosL is resolved as com.sun.tools.javac.code.Symbol$ClassSymbol and Element.asType() is
com.sun.tools.javac.code.Type$ErrorType. This is certainly a bug, there are no errors in the source code.

java CUPS can be downloaded from http://www2.cs.tum.edu/projects/cup/, or I can provide a NetBeans project for that, if
necessary.
Comment 1 Martin Entlicher 2008-02-13 14:47:56 UTC 
Created attachment 56609 [details]
php.parser project.
Comment 2 Martin Entlicher 2008-02-13 15:06:43 UTC 
Workaround in debugger is implemented, error elements are recognized here:
changeset:   67163:6bbc2271729c
http://hg.netbeans.org/main/rev/6bbc2271729c
Comment 3 Jan Lahoda 2008-02-14 09:41:23 UTC 
I have opened the file and took a look at the given identifier in the Trees navigator view, and it looked OK. So we will
need more info on when exactly the problem happens. Automated test case would be perfect, but end user instructions to
reproduce, so that we can debug what is happening, are fine too.
Comment 4 Jiri Prox 2008-12-05 14:18:36 UTC 
Is this issue still valid? There is quiet for a very long time.
Comment 5 Rastislav Komara 2009-02-03 10:53:24 UTC 
Overtake.
Comment 6 Rastislav Komara 2009-03-24 10:57:11 UTC 
planing to future. still awaiting reporter interaction.
Comment 7 David Strupl 2009-03-31 16:00:11 UTC 
Resolving all issues with milestone "future" as LATER. If you feel strongly that
it should be implemented please reopen and set the target milestone to "next".
Comment 8 Quality Engineering 2009-11-02 10:57:25 UTC 
NetBeans.org Migration: changing resolution from LATER to WONTFIX