[Supersize] Fix incorrect normalization of thin archive paths.
Strings in |MapFileParser| may contain concated thin archive paths like
"path/to/lib.a(../../path/to/object.o)". Normpath treats it as a path
and resolves second .. by removing the "lib.a(.." part. It breaks thin
archives processing, resulting in exceptions up the stack in |archive|
on calls to "rindex('(')".
Solution: thin archive paths do already get their paths normalized
later in |ar.CreateThinObjectPath|. So just skip them at this point.
R=huangs@chromium.org,agrieve@chromium.org
Change-Id: I83bffca44eba2a56c0ffdbfc8c83cd2785fb8b56
Reviewed-on: https://chromium-review.googlesource.com/1140298Reviewed-by:
agrieve <agrieve@chromium.org>
Reviewed-by:
Samuel Huang <huangs@chromium.org>
Commit-Queue: agrieve <agrieve@chromium.org>
Cr-Commit-Position: refs/heads/master@{#575631}
Showing
Please register or sign in to comment