diff options
| author | Jason Zaugg <jzaugg@gmail.com> | 2015-04-25 22:02:16 +1000 |
|---|---|---|
| committer | Jason Zaugg <jzaugg@gmail.com> | 2015-04-27 08:33:20 +1000 |
| commit | 3ecbe596faf9f7b103856d3298eb0325bd5dc294 (patch) | |
| tree | 77c4b2ad89dedd031d20d0c6803c62b6cffd10f9 /Gemfile | |
| parent | d063dd32098f1dacdb13fb6bd750a75a444dcacd (diff) | |
| download | scala-3ecbe596faf9f7b103856d3298eb0325bd5dc294.tar.gz scala-3ecbe596faf9f7b103856d3298eb0325bd5dc294.tar.bz2 scala-3ecbe596faf9f7b103856d3298eb0325bd5dc294.zip | |
SI-9282 Avoid obscuring an exception during classfile parsing
Based on analysis of a stack trace in this bug report, I identified
a code path in `ClassfileParser` that can lead to an NPE in its
exception handling code. If `val in = new AbstractFileReader(file)`
throws (e.g during its construction in which it eagerly reads the
file `val buf: Array[Byte] = file.toByteArray`), the call to
`in.file` in `handleError` will NPE.
This commit stores the active file directly a field in ClassfileParser
and uses this in the error reporting.
Diffstat (limited to 'Gemfile')
0 files changed, 0 insertions, 0 deletions