Re: [rvm-research] Exception while executing Junit Test Cases while running pre-commit

Hi,

On 27.04.2013 13:07, Pushparaj Motamari wrote:
> I have modified the Jikes, and this is exception is not shown when I do
> wth unmodified VM

In this case, you can use the unmodified Jikes RVM (or a modified
version in which the problem does not occur) as a basis for getting a
diff. Once you have a diff, you can narrow it down until you have
isolated the code changes that caused the problem. Then you "only" need
to find out why the changes are a problem.

>From your earlier mails I take it that you are doing some kind of
instrumentation. In that case, one possibility is that you're
instrumenting code that you don't want to (or should not) instrument.
Michael Bond has already mentioned some useful conditions that you can
check in the compiler to determine if you're instrested in the code in
question (see the mailing list thread about VM.sysWriteln()).
Additionally, you can also check if the compilers are being run during
bootimage writing or at runtime by checking VM.RunningVM.

IMHO the easiest way to debug the RVM code is to use assertions and
printouts to figure out what is going on. Some of the command line
options that the Jikes RVM provides may also be useful.

When making changes, it's advisable to take small steps. If you can test
your changes using automated tests, you should do so because it'll
probably save you time in the long run.

I'm afraid I can't give you any more specific advice without any
knowledge about the modifications you have done to the Jikes RVM.


Kind regards,

Erik Brangs

------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr