On Wed, Aug 26, 2009 at 6:57 PM, Matthew
Toseland<toad at amphibian.dyndns.org> wrote:
> freenet-ext.jar 27pre4 is now available. Please test it! This supports 
> FreeBSD on x86 (thanks to Artefact2), and it has x86-64 native FEC that 
> hopefully doesn't segfault any more (thanks infinity0). Please try it, and 
> report any problems.
>

Got a problem here.

INFO   | jvm 1    | 2009/08/26 19:54:49 | # A fatal error has been
detected by the Java Runtime Environment:
INFO   | jvm 1    | 2009/08/26 19:54:49 | #
INFO   | jvm 1    | 2009/08/26 19:54:49 | #
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x21bf18a9, pid=292,
tid=4572
INFO   | jvm 1    | 2009/08/26 19:54:49 | #
INFO   | jvm 1    | 2009/08/26 19:54:49 | # JRE version: 6.0_15-b03
INFO   | jvm 1    | 2009/08/26 19:54:49 | # Java VM: Java HotSpot(TM)
Client VM (14.1-b02 mixed mode windows-x86 )
INFO   | jvm 1    | 2009/08/26 19:54:49 | # Problematic frame:
INFO   | jvm 1    | 2009/08/26 19:54:49 | # C
[libfec5080962777883551596.tmp+0x18a9]
INFO   | jvm 1    | 2009/08/26 19:54:49 | #
INFO   | jvm 1    | 2009/08/26 19:54:49 | # An error report file with
more information is saved as:
INFO   | jvm 1    | 2009/08/26 19:54:49 | # F:\Freenet\hs_err_pid292.log
INFO   | jvm 1    | 2009/08/26 19:54:49 | #
INFO   | jvm 1    | 2009/08/26 19:54:49 | # If you would like to
submit a bug report, please visit:
INFO   | jvm 1    | 2009/08/26 19:54:49 | #
http://java.sun.com/webapps/bugreport/crash.jsp
INFO   | jvm 1    | 2009/08/26 19:54:49 | # The crash happened outside
the Java Virtual Machine in native code.
INFO   | jvm 1    | 2009/08/26 19:54:49 | # See problematic frame for
where to report the bug.
INFO   | jvm 1    | 2009/08/26 19:54:49 | #
ERROR  | wrapper  | 2009/08/26 19:54:49 | JVM exited unexpectedly.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: hs_err_pid292.log
Type: application/octet-stream
Size: 23448 bytes
Desc: not available
URL: 
<https://emu.freenetproject.org/pipermail/devl/attachments/20090826/871efefc/attachment.obj>

Reply via email to