If there is an error reading or parsing an archive header, the
Archive_iterator code would return a dummy header but would not mark
itself as done. The effect is that an invalid archive leads to an
endless loop reading and re-reading the same archive header. Avoid
that by setting the offset to the end of the file, which will cause
the iterator to == archive_end.
No test since it doesn't seem worth constructing an invalid archive.
Reviewed-on: https://go-review.googlesource.com/c/158217
From-SVN: r268129
| Name |
Last commit
|
Last update |
|---|---|---|
| .. | ||
| gofrontend | Loading commit data... | |
| ChangeLog | Loading commit data... | |
| Make-lang.in | Loading commit data... | |
| README.gcc | Loading commit data... | |
| config-lang.in | Loading commit data... | |
| gccgo.texi | Loading commit data... | |
| go-backend.c | Loading commit data... | |
| go-c.h | Loading commit data... | |
| go-gcc-diagnostics.cc | Loading commit data... | |
| go-gcc.cc | Loading commit data... | |
| go-gcc.h | Loading commit data... | |
| go-lang.c | Loading commit data... | |
| go-linemap.cc | Loading commit data... | |
| go-location.h | Loading commit data... | |
| go-sha1.cc | Loading commit data... | |
| go-system.h | Loading commit data... | |
| gospec.c | Loading commit data... | |
| lang-specs.h | Loading commit data... | |
| lang.opt | Loading commit data... |