harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexei Fedotov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-5099) [drlvm][jvmti] methods on stack while debugging are incorrectly shown as obsolete and native
Date Thu, 08 Nov 2007 22:51:50 GMT

    [ https://issues.apache.org/jira/browse/HARMONY-5099?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12541168
] 

Alexei Fedotov commented on HARMONY-5099:
-----------------------------------------

Gregory suggested returning JNI_FALSE from jvmtiIsMethodObsolete function. Actually the last
return is unreachable due to CHECK_CAPABILITY(can_redefine_classes) which returns error. I
have noticed that commenting CHECK_CAPABILITY(can_redefine_classes) makes the stack trace
correct.

My current assumption is that the Eclipse agent incorrectly processes a return code. We may
also say that Eclipse just migrated to the newer version of Java since starting from Java
6.0 IsMethodObsolete method no longer requires the capability.

> [drlvm][jvmti] methods on stack while debugging are incorrectly shown as obsolete and
native
> --------------------------------------------------------------------------------------------
>
>                 Key: HARMONY-5099
>                 URL: https://issues.apache.org/jira/browse/HARMONY-5099
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: Windows ia32
>            Reporter: Alexei Fedotov
>
> While debugging AWT drag and drop application with DRLVM I'm getting the following stack
traces:
> Daemon Thread [AWT-EventDispatchThread] (Suspended (exception NullPointerException))

> 	DataSource.Obsolete method() line: not available [native method]	
> 	DataSnapshot.Obsolete method() line: not available [native method]	
> 	WinDragSource.Obsolete method() line: not available [native method]	
> 	DragSource.Obsolete method() line: not available [native method]	
> 	DragSource.Obsolete method() line: not available [native method]	
> 	DragSource.Obsolete method() line: not available [native method]	
> 	DragGestureEvent.Obsolete method() line: not available [native method]	
> 	dnd.Obsolete method() line: not available [native method]	
> 	DragGestureRecognizer.Obsolete method() line: not available [native method]	
> 	DefaultMouseDragGestureRecognizer.Obsolete method() line: not available [native method]

> 	Component.Obsolete method() line: not available [native method]	
> 	Component.Obsolete method() line: not available [native method]	
> 	Component.Obsolete method() line: not available [native method]	
> 	Button.Obsolete method() line: not available [native method]	
> 	Component.Obsolete method() line: not available [native method]	
> 	EventQueueCore.Obsolete method() line: not available [native method]	
> 	EventQueue.Obsolete method() line: not available [native method]	
> 	EventDispatchThread.Obsolete method() line: not available [native method]	
> Actual methods are both not obsolete and not native. 
> 	EventDispatchThread.Obsolete method() line: not available [native method]	

-- 
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