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.
Summary: | java.lang.IllegalArgumentException: Unknown type: 10 | ||
---|---|---|---|
Product: | java | Reporter: | tboerkel <tboerkel> |
Component: | Source | Assignee: | Jan Lahoda <jlahoda> |
Status: | VERIFIED FIXED | ||
Severity: | blocker | CC: | jglick |
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows Vista | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
I am getting LOTS of those exceptions while sources are being scanned.
Base64.dump Base64.java Base64.class Signature files |
Description
tboerkel
2007-01-03 12:21:17 UTC
Created attachment 37006 [details]
I am getting LOTS of those exceptions while sources are being scanned.
It's worse than I thought. I also get these exceptions on every incovation of code completion and while editing. It then leaves a .dump file of the edited source in var\log. Attaching example "Base64.dump", "Base64.java", "Base64.class". Created attachment 37007 [details]
Base64.dump
Created attachment 37008 [details]
Base64.java
Created attachment 37009 [details]
Base64.class
Can you attach the signature files for the broken source root? The signature files are located in the nbuser dir under var/cache/index/1.0/${ID}/classes folder. The ID can be found in the var/cache/index/1.0/segments file, which has the following format: ID=URL. Created attachment 37011 [details]
Signature files
Seems that the sig files were sometimes incorrectly generated. I attempted to fix this problem. Please delete you caches ($userdir/vat/cache/index/0.1) to remove the incorrect files and start the IDE again. Please reopen if it happens again. Thanks. Checking in src/org/netbeans/modules/java/source/usages/SymbolDumper.java; /cvs/java/source/src/org/netbeans/modules/java/source/usages/SymbolDumper.java,v <-- SymbolDumper.java new revision: 1.3; previous revision: 1.2 done Verified, though there are other warnings now; see latest attachment to issue #49371. |