This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
java_class_process [2013/04/29 08:30] yann |
java_class_process [2013/04/29 08:32] yann |
||
---|---|---|---|
Line 25: | Line 25: | ||
===== The Bug ===== | ===== The Bug ===== | ||
- | When applying [[MoDeC]] on "small" program, we did not encounter any problem, neither on Windows nor on Mac OS. However, when Soumaya ran [[MoDeC]] on the instrumented version of ArgoUML v0.19.8, should got this exception (here reproduced using Venera's Mac): | + | When applying [[MoDeC]] on "small" programs, we did not encounter any problem, neither on Windows nor on MacOS. However, when Soumaya ran [[MoDeC]] on the instrumented version of ArgoUML v0.19.8, she got this exception (here reproduced using Venera's Mac): |
<code> | <code> | ||
Line 38: | Line 38: | ||
</code> | </code> | ||
- | which was very puzzling because the version of [[MoDeC]] and the same input file and the same instrumented bytecodes would work on Yann's Windows laptop and produce the expected traces. | + | which was very puzzling, because the //same// version of [[MoDeC]] and the //same// input file and the //same// instrumented bytecodes would work on Yann's Windows laptop and produce the expected traces. |
===== The Solution ===== | ===== The Solution ===== |