Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.java.programmer > #16020
| From | markspace <-@.> |
|---|---|
| Newsgroups | comp.lang.java.programmer |
| Subject | Re: Tracing rt.jar? |
| Date | 2012-07-14 09:44 -0700 |
| Organization | A noiseless patient Spider |
| Message-ID | <jts7l1$ct4$1@dont-email.me> (permalink) |
| References | <spy-20120714182301@ram.dialup.fu-berlin.de> |
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.
Back to comp.lang.java.programmer | Previous | Next — Next in thread | Find similar | Unroll thread
Re: Tracing rt.jar? markspace <-@.> - 2012-07-14 09:44 -0700 Re: Tracing rt.jar? markspace <-@.> - 2012-07-14 10:57 -0700
csiph-web