ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 15230] - TAR long path names (GNU format) append a trailing 0 char
Date Fri, 18 Apr 2003 08:41:10 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15230>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15230

TAR long path names (GNU format) append a trailing 0 char





------- Additional Comments From jdb@getsu.com  2003-04-18 08:41 -------
This fix isn't in 1.5.3 either.  What's the matter?

Impact:
When ant untars a path over 100 chars long, it writes the path with a
terminating 0 char into its XML log.  This 0 char should not be part of the
path, and it breaks tools that parse ant's log (like CruiseControl).

Root cause:
A long path in a tar file includes a terminating 0 char.  TarInputStream
includes that char in the path name.  This looks like a bug in porting tar
source from C to Java.  Strings require a terminating 0 in C but not Java.

Reproduction:
See the JUnit test previously posted.

Suggested fix:
See the patch previously posted.

Thanks,
11011011

Mime
View raw message