harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gregory Shimansky (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HARMONY-1847) [drlvm] -verbose option does nothing
Date Fri, 24 Nov 2006 22:02:05 GMT
     [ http://issues.apache.org/jira/browse/HARMONY-1847?page=all ]

Gregory Shimansky resolved HARMONY-1847.

    Resolution: Fixed

This patch causes crash on trace in classloader.cpp (I tried -Xtrace:classloader) on x86_64.
However it doesn't seem to be the patch fault. Classloader somehow operates with 32-bit points
which doesn't seem to be a right thing to do. Also I saw some 32-bit pointers in the crash
stack too. Probably not all x86_64 support bugs were found yet. I've used -Xtrace:init instead
and it worked.

Patch applied at 479014. Please check that it was applied as expected.

> [drlvm] -verbose option does nothing
> ------------------------------------
>                 Key: HARMONY-1847
>                 URL: http://issues.apache.org/jira/browse/HARMONY-1847
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Any just java -version test
>            Reporter: Jean-Frederic Clere
>         Assigned To: Gregory Shimansky
>            Priority: Minor
>         Attachments: log4cxx-fix.patch, update-log4cxx-revision.patch, workaround-fflush-log.patch
> java -verbose does not print any information
> To debug an application it is very helpfull to know which classes and in which order
they are loaded.
> Something like what RI gives would be enough.
> [Opened C:\tools\sun1.5.0\jre\lib\rt.jar]
> [Opened C:\tools\sun1.5.0\jre\lib\charsets.jar]
> [Loaded java.lang.Object from C:\tools\sun1.5.0\jre\lib\rt.jar]
> [Loaded java.io.Serializable from C:\tools\sun1.5.0\jre\lib\rt.jar]
> [Loaded java.lang.Comparable from C:\tools\sun1.5.0\jre\lib\rt.jar] 
> Xtrace:classloader contains the information but it is too verbose.

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


View raw message