You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Salikh Zakirov (JIRA)" <ji...@apache.org> on 2006/07/12 15:44:30 UTC

[jira] Updated: (HARMONY-853) [build/archive] DRLVM+classlib segfaults in hyzlib

     [ http://issues.apache.org/jira/browse/HARMONY-853?page=all ]

Salikh Zakirov updated HARMONY-853:
-----------------------------------

    Attachment: 0001-added-overridable-LDFLAGS-in-rules.mk-use-Bsymbolic-for-hyzlib.patch

The simple addition of -Bsymbolic to linker flags of hyzlib solves the problem.

I would suggest to apply this patch until the problem is solved in a "proper" way of removing duplication hyzlib - system libz

> [build/archive] DRLVM+classlib segfaults in hyzlib
> --------------------------------------------------
>
>          Key: HARMONY-853
>          URL: http://issues.apache.org/jira/browse/HARMONY-853
>      Project: Harmony
>         Type: Bug

>   Components: Classlib
>  Environment: Linux/i686,  SLES 9 (Suse Linux Enterprise Server), libc 2.3.3, gcc 3.3.3, libz 1.2.1
>     Reporter: Salikh Zakirov
>  Attachments: 0001-added-overridable-LDFLAGS-in-rules.mk-use-Bsymbolic-for-hyzlib.patch
>
> I do not know for sure what is the cause of the segfaults.
> The stack trace of the segfault is below, though I doubt it means too much
> #0  0x54e68cf7 in inflate ()
>    from .../jre/bin/libhyzlib.so
> #1  0x55b679a9 in inflateData ()
>    from .../jre/bin/libhyarchive.so
> #2  0x55b6989b in zip_getZipEntryData ()
>    from .../jre/bin/libhyarchive.so
> #3  0x55b6500c in Java_java_util_zip_ZipFile_inflateEntryImpl2 ()
>    from .../jre/bin/libhyarchive.so
> #4  0x40b30d4e in invokeJNI ()
> The problem has a known workaround: to compile hyzlib with -Bsymbolic linker flag
> in order to perform internal linking in hyzlib at link time rather than at runtime.
> I've heard informal reports from Gregory that the problem is not reproducible on Gentoo (with latest versions of all libraries)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira