Fwd: Emma Problem

29 views
Skip to first unread message

Terence Statt

unread,
Jun 2, 2008, 12:14:14 PM6/2/08
to 308clas...@googlegroups.com


---------- Forwarded message ----------
From: Richard <ri...@thepit.org>
Date: Mon, Jun 2, 2008 at 8:45 AM
Subject: RE: Emma Problem
To: Terence Statt <csk...@gmail.com>


ok you have three problems.
 
1)  you're including non-jalopy/fixstyle classes in the instrumentation path, see if you can filter those out with -ix -<filterstring> or include only those files you want with -ix +<filterstring>
 
2)  you jarred up the emma class files with your fixstyle class files before instrumenting the jar, this is bad.  instrument fixstyle before jarring up the emma files with it.
 
3)  you haven't compiled the source files with debug information, by default eclipse does this which is why we haven't experienced this problem but, you can try modifying your build or making a new build script that compiles with debug info so that emma knows what line corresponds to what instructions.
 
happy hunting
 

---------------------------------
Richard McDaniel
ric...@san.rr.com

Rule 1:  The DM is always right.
Rule 2:  If the DM is wrong refer to rule 1
Rule 3:  If all else fails, buy the DM a Pizza

 


From: Terence Statt [mailto:csk...@gmail.com]
Sent: June 1, 2008 10:53 PM
To: rmcd...@calpoly.edu
Cc: Jim
Subject: Emma Problem

Hi:
I'm not sure if Jim made any more progress with Emma, but I am getting this error with it.  I looked up online how to instrument a .jar file and on the class tutorial and the commands are slightly different but produce the same error.  The error seems to be the problem that Richard mentioned about Emma not having access to files.  So, hopefully you don't mind me taking your e-mail off the contact page to ask you if you know how to easily fix this problem.  I copied in all the files of Emma into our .jar along with the Emma jar and still got this error.  I tried one, then the other, and then both and still got this error.
Here are the two commands that I tried:

C:\BlueJ\lib\extensions>java -cp emma-2.0.5312\lib\emma.jar;.;.
\Fixstyle.jar emma instr -ip .\F
ixstyle.jar -m overwrite
C:\BlueJ\lib\extensions>java -cp emma-2.0.5312\lib\emma.jar emma instr -m overwrite -cp ./Fixst
yle.jar

(Yeah, ignore the line wrapping, its windows command line which has a set of like 80 characters long and you can't expand it.  Sorry)
Below is the same error message that I get.  Does anyone know how to stop this or get around this?  Maybe this enough for someone to take it since I took it this far and continue.

EMMA: processing instrumentation path ...
EMMA: package [org/apache/log4j/jmx] contains classes [AbstractDynamicMBean] without full debug
 info
EMMA: package [org/apache/log4j/net] contains classes [DefaultEvaluator] without full debug inf
o
EMMA: package [org/apache/log4j/xml] contains classes [XMLLayout] without full debug info
EMMA: package [] contains classes [Fixstyle] without full debug info
EMMA: package [de/hunsicker/io] contains classes [Copy] without full debug info
EMMA: package [de/hunsicker/jalopy] contains classes [Jalopy$SpyAppender] without full debug in
fo
EMMA: package [de/hunsicker/jalopy/language] contains classes [Annotation] without full debug i
nfo
EMMA: package [de/hunsicker/jalopy/language/antlr] contains classes [InternalJavaLexer] without
 full debug info
EMMA: package [de/hunsicker/jalopy/plugin] contains classes [AbstractAppender] without full deb
ug info
EMMA: package [de/hunsicker/jalopy/prefs] contains classes [Key] without full debug info
EMMA: package [de/hunsicker/jalopy/printer] contains classes [AbstractPrinter] without full deb
ug info
EMMA: package [de/hunsicker/jalopy/storage] contains classes [Convention$Key] without full debu
g info
EMMA: package [de/hunsicker/jalopy/swing] contains classes [AbstractSettingsPage$1] without ful
l debug info
EMMA: package [de/hunsicker/jalopy/swing/syntax] contains classes [DefaultSyntaxDocument$Docume
ntHandler] without full debug info
EMMA: package [de/hunsicker/swing] contains classes [DirectoryPanel] without full debug info
EMMA: package [de/hunsicker/swing/util] contains classes [PopupSupport$1] without full debug in
fo
EMMA: package [de/hunsicker/util] contains classes [ChainingRuntimeException] without full debu
g info
EMMA: package [de/hunsicker/util/concurrent] contains classes [FutureResult$1] without full deb
ug info
EMMA: package [edu/calpoly/twain/Fixstyle] contains classes [DefaultLoader$1] without full debu
g info
EMMA: EMMA classes appear to be included on the instrumentation
EMMA: path: this is not a correct way to use EMMA
[EMMA v2.0, build 5312]
emma instr: could not rename temporary file [C:\BlueJ\lib\extensions\Fixstyleemma32662.et] to [
C:\BlueJ\lib\extensions\Fixstyle.jar]: make sure the original file is not locked and can be del
eted
Exception in thread "main" com.vladium.emma.EMMARuntimeException: could not rename temporary fi
le [C:\BlueJ\lib\extensions\Fixstyleemma32662.et] to [C:\BlueJ\lib\extensions\Fixstyle.jar]: ma
ke sure the original file is not locked and can be deleted
        at com.vladium.emma.instr.InstrProcessorST.handleArchiveEnd(InstrProcessorST.java:375)
        at com.vladium.util.IPathEnumerator$Factory$PathEnumerator.enumerate(IPathEnumerator.ja
va:114)
        at com.vladium.emma.instr.InstrProcessorST._run(InstrProcessorST.java:715)
        at com.vladium.emma.Processor.run(Processor.java:54)
        at com.vladium.emma.instr.instrCommand.run(instrCommand.java:163)
        at emma.main(emma.java:40)

--
Terence Statt
510-557-5318
Csk...@gmail.com

No virus found in this incoming message.
Checked by AVG.
Version: 8.0.100 / Virus Database: 269.24.4/1477 - Release Date: 6/1/2008 5:28 PM




--
Terence Statt
510-557-5318
Csk...@gmail.com
Reply all
Reply to author
Forward
0 new messages