HotSpot Warning

I occasionally get messages like the following when using hotspot. is it something I should worry about, and write up a tracker for? Or can I just ignore it.

Thanks,
Mike

-



Warning: (356,1) MethodSignature: addSaveFileToZip(): method is obsolete

3 comments
Comment actions Permalink

Yep, this is a normal situation: you receive a warning that the method you are stepping in is obsolete (the method has been
hot-swapped).

--

Best regards,
Eugene Zhuravlev
JetBrains, Inc, http://www.intellij.com
"Develop with pleasure!"

"Michael Kirby" <kirby@ess.mc.xerox.com> wrote in message news:2632422.1063117522348.JavaMail.itn@is.intellij.net...

I occasionally get messages like the following when using hotspot. is it something I should worry about, and write up a tracker

for? Or can I just ignore it.
>

Thanks,
Mike

>

------

>

Warning: (356,1) MethodSignature: addSaveFileToZip([PsiType:Set, PsiType:MMFileType,

PsiType:int,PsiType:Compressor,PsiType:ZipOutputStream,PsiType:File]): method is obsolete
>
>


0
Comment actions Permalink

Yep, this is a normal situation: you receive a
warning that the method you are stepping in is
obsolete (the method has been
hot-swapped).


Hmm...From the users perspective, the message doesn't say much. How about "Current debugging state is obsoletel: Method XXX replaced"

Or some such message.

Mike

0
Comment actions Permalink

Quite the contrary, method was not replaced! JVM do not replace currently executed methods. It will replace the method after execution exit from it.

This means, that currently executed methods become obsolete. They do not correspond to their .class files and sources.

The debugging state is not obsolete. It is too modern. Debugger steps through obsolete methods using modern (current) sources and that is the problem that it warns about.

PS. I agree method name should be in more readable format (soon I'll fix that).

0

Please sign in to leave a comment.