Groups > comp.lang.java.programmer > #16020 > unrolled thread

Re: Tracing rt.jar?

Started by	markspace <-@.>
First post	2012-07-14 09:44 -0700
Last post	2012-07-14 10:57 -0700
Articles	2 — 1 participant

Back to article view | Back to comp.lang.java.programmer

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

  Re: Tracing rt.jar? markspace <-@.> - 2012-07-14 09:44 -0700
    Re: Tracing rt.jar? markspace <-@.> - 2012-07-14 10:57 -0700

#16020 — Re: Tracing rt.jar?

From	markspace <-@.>
Date	2012-07-14 09:44 -0700
Subject	Re: Tracing rt.jar?
Message-ID	<jts7l1$ct4$1@dont-email.me>

On 7/14/2012 9:28 AM, Stefan Ram wrote:
>    Is there an rt.jar somewhere out there than can replace the
>    standard rt.jar, but was instrumented to trace° all incoming¹
>    calls with their argument values? Or some other technique

Hmm, you can step into rt.jar with a debugger, and if you have the 
source loaded it will at least show you what lines are executed branches 
are taken (although local variables have been optimized away).

I've also accidentally enabled "FINEST" level of debuging for java.* 
files and gotten quite a lot of spew.  That won't work if the classes 
you are interested in don't log, but it might be worth a shot.

I don't know of anything that specifically does what you want, although 
if you look into aspect oriented programming I think they might have 
something there that can auto-magically instrument a .jar file with 
logging.  This would be a lot easier than trying to do the byte code 
re-writting yourself.

Can you tell us specifically why you need this?  What's the use case, 
model, or failure mode here?  You question is kind of general.

[toc] | [next] | [standalone]

#16023

From	markspace <-@.>
Date	2012-07-14 10:57 -0700
Message-ID	<jtsbth$6lp$1@dont-email.me>
In reply to	#16020

On 7/14/2012 9:54 AM, Stefan Ram wrote:
> markspace <-@.> writes:
>> Can you tell us specifically why you need this?  What's the use case,
>> model, or failure mode here?  You question is kind of general.
>
>    To analyze an Java applet. I /can/ already enable the finest
>    trace level in the Browser's Java console and enable
>    logging, but that does not show that much. The class files
>    are obfuscated. The idea is to learn how the applet
>    accomplishes certain tasks.
>

Is it your applet, or are you actually analyzing something that someone 
else wrote?  Do you have access to the applet source?

Just curious: are there any DMCA issues involved here, or EULA issues, 
per chance?

Have you considered running the applet outside of a browser?  It's just 
code you can download and run in any JVM.  How much work are you willing 
to put into this?

[toc] | [prev] | [standalone]

csiph-web

Re: Tracing rt.jar?

Contents

#16020 — Re: Tracing rt.jar?

#16023