Do you have a reference to the bug?
This is still a very early version of java 7. It would be good to update
it.
On Tue, Feb 5, 2013 at 5:49 PM, Jesse Glick wrote:
> On 02/05/2013 07:30 PM, sebb wrote:
>
>> a pure Java application should not be able to cause a JVM crash
>>
>
> Depends entirely
On 6 February 2013 01:49, Jesse Glick wrote:
> On 02/05/2013 07:30 PM, sebb wrote:
>>
>> a pure Java application should not be able to cause a JVM crash
>
>
> Depends entirely on what you mean by “pure Java application”. When you have
> filesystem and Process access, you can do whatever the user s
On 02/05/2013 07:30 PM, sebb wrote:
a pure Java application should not be able to cause a JVM crash
Depends entirely on what you mean by “pure Java application”. When you have filesystem and Process access, you can do whatever the user shell account can do, which
certainly includes triggering
On 5 February 2013 17:59, Jesse Glick wrote:
> On 02/04/2013 09:23 AM, Martin Desruisseaux wrote:
>>
>> the crash occurs in the C/C++ implementation of
>> java.util.zip.ZipFile.getEntry(String)
>
>
> This is almost always a symptom of user error rather than a JDK bug; or at
> least any bug report
Thanks. It helped.
On Mon, Feb 4, 2013 at 11:58 PM, Niklas Gustavsson wrote:
> On Tue, Feb 5, 2013 at 2:32 AM, Ted Dunning wrote:
> > There are three builds running on ubuntu4. Two have been running for
> over
> > 30 hours. One has been running for nearly 8 hours.
>
> Killed and cleaned up.
>
On 02/04/2013 09:23 AM, Martin Desruisseaux wrote:
the crash occurs in the C/C++ implementation of
java.util.zip.ZipFile.getEntry(String)
This is almost always a symptom of user error rather than a JDK bug; or at least any bug report to Oracle along these lines will be rejected. Something in y
