harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Created: (HARMONY-5358) [classlib][luni] hyluni lib crashes if bootclasspath.properties has blanks-only line
Date Sat, 29 Dec 2007 10:13:43 GMT
[classlib][luni] hyluni lib crashes if bootclasspath.properties has blanks-only line
------------------------------------------------------------------------------------

                 Key: HARMONY-5358
                 URL: https://issues.apache.org/jira/browse/HARMONY-5358
             Project: Harmony
          Issue Type: Bug
          Components: Classlib
    Affects Versions: 5.0M4
         Environment: unix
            Reporter: Alexey Varlamov


luni native lib crashes during initialization if bootclasspath.properties file contains a
line with only spaces in it, due to freeing invalid pointer.
Here is a part of DRLVM backtrace:
#7  0x00002b8ac207135b in __libc_message () from /lib64/libc.so.6
#8  0x00002b8ac207634e in malloc_printerr () from /lib64/libc.so.6
#9  0x00002b8ac1ec0737 in hymem_free_memory (portLibrary=0x7fffe9130f10, memoryPointer=0x2aaabdd9f773)
at hymem.c:112
#10 0x00002aaabdd7b76d in readClassPathFromPropertiesFile (vmInterface=0x2aaabdd6b400) at
../shared/luniglob.c:370
#11 0x00002aaabdd7aec9 in JNI_OnLoad (vm=0x52d088, reserved=0x0) at ../shared/luniglob.c:128
#12 0x00002aaaaabfe501 in find_call_JNI_OnLoad (lib_handle=0x57c398)
    at /export/users/avarlamo/trunk/working_vm/vm/vmcore/src/util/natives_support.cpp:120
#13 0x00002aaaaabfe83e in natives_load_library (library_name=0x52f560 "libhyluni.so", just_loaded=0x7fffe91307cf,
    pstatus=0x7fffe91307c8) at /export/users/avarlamo/trunk/working_vm/vm/vmcore/src/util/natives_support.cpp:293
#14 0x00002aaaaab45bf9 in ClassLoader::LoadNativeLibrary (this=0x540050, name=0x591b07 "libhyluni.so")
    at /export/users/avarlamo/trunk/working_vm/vm/vmcore/src/class_support/classloader.cpp:1025
#15 0x00002aaaaab4b265 in BootstrapClassLoader::Initialize (this=0x540050, loader=0x0)
    at /export/users/avarlamo/trunk/working_vm/vm/vmcore/src/class_support/classloader.cpp:1359
#16 0x00002aaaaac33c89 in bootstrap_initial_java_classes (vm_env=0x52d0b8)
    at /export/users/avarlamo/trunk/working_vm/vm/vmcore/src/init/vm_init.cpp:358
#17 0x00002aaaaac33ef3 in preload_classes (vm_env=0x52d0b8)
    at /export/users/avarlamo/trunk/working_vm/vm/vmcore/src/init/vm_init.cpp:400
#18 0x00002aaaaac34d3b in vm_init1 (java_vm=0x52d088, vm_arguments=0x7fffe9130cb0)
    at /export/users/avarlamo/trunk/working_vm/vm/vmcore/src/init/vm_init.cpp:835

I just wonder why it does not affect windows builds, and why we're so lucky to not discover
such an old and stupid bug earlier...

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message