Red Hat Bugzilla – Bug 466034
SIGSEGV from memcpy using ZipFile.getNextEntry on Linux
Last modified: 2009-12-18 01:31:34 EST
Created attachment 319690 [details]
Description of problem:
The SIGSEGV occurs after overwriting/modifying a jar file with new content and then try to read the entries after modification.
Version-Release number of selected component (if applicable):
OpenJDK Server VM (1.6.0-b09) for linux-x86 JRE (1.6.0-b09)
Sun Java HotSpot(TM) Server VM (10.0-b19) for linux-x86 JRE (1.6.0_05-b13)
Problem not seen with BEA jrockit-jdk1.6.0_05
Have one test case that can reproduce as noted in:
Steps to Reproduce:
The above JIRA references a test case that can consistently reproduce the problem. I'll write a test program to simulate the test code and attach once I can reproduce it consistently. The second JBoss post listed has steps to reproduce.
Is there a testcase for this?
Lillian, I attempted to create a standalone test case to show the problem and even though I wrote one, it did not provoke the VM crash as seen with the AS testsuite consistently. The JBOSS forum posts referenced above have explicit steps but using VFS still.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
Created attachment 337018 [details]
Attaching a test case that works for me. It may requires a few runs for it to demonstrate the issue. It requires two jar files to work: original.jar.orig and fake.jar (the program copies original.jar.orig to original.jar and then overwrites it with fake.jar) If original.jar.orig is much bigger than fake.jar, than the program crashes. If fake.jar is much bigger than original.jar.orig, it will produce corrupted output. If the program crashes, it's in libzip.so. It looks like libzip caches information about the file and doesnt expect the file to change.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.