[
https://issues.apache.org/jira/browse/COMPRESS-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864194#action_12864194
]
Jukka Zitting commented on COMPRESS-75:
---------------------------------------
Is there anything else we need to do for this?
> ZipArchiveInputStream does not show location in file where a problem occurred
> -----------------------------------------------------------------------------
>
> Key: COMPRESS-75
> URL: https://issues.apache.org/jira/browse/COMPRESS-75
> Project: Commons Compress
> Issue Type: Bug
> Affects Versions: 1.0
> Reporter: Sebb
> Fix For: 1.1
>
>
> See COMPRESS-62 - if ExtraFieldUtils.parse() detects an error, it only shows
> the offset within the local buffer, which is fairly useless in tracking down
> a problem.
> Somehow the current location in the file needs to be determined and added to
> the Exception message.
> The count/bytesRead field would help, but that actually points to the next
> available byte, i.e. after the problem area.
> Also, the internal data may have been expanded.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
