Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Found no new log entries -- always #6

Open
manasthakur opened this issue Oct 24, 2016 · 8 comments
Open

Found no new log entries -- always #6

manasthakur opened this issue Oct 24, 2016 · 8 comments

Comments

@manasthakur
Copy link

I am using the play-out agent for DaCapo benchmarks. For whichever benchmark I run it, the reflection log is empty with the message "Found no new log entries". Is this a problem?

@ericbodden
Copy link
Member

Well that certainly sounds wrong. Might there be a problem with your poa.properties file?

Cheers
Eric

On 24.10.2016, at 11:03, Manas Thakur [email protected] wrote:

I am using the play-out agent for DaCapo benchmarks. For whichever benchmark I run it, the reflection log is empty with the message "Found no new log entries". Is this a problem?


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@manasthakur
Copy link
Author

manasthakur commented Oct 26, 2016

I have not included a poa.properties file. Just following the instructions on the DaCapoAndSoot wiki page.

Regards,
Manas

@ericbodden
Copy link
Member

Ok can you please look at the poa.properties file in your installation to see which instrumentations are enabled?

Cheers
Eric

On 26.10.2016, at 08:56, Manas Thakur [email protected] wrote:

I have not included any poa.properties file. Just following the instructions on the DaCapoAndSoot wiki page.

Regards,
Manas


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@manasthakur
Copy link
Author

Hi Eric,

The contents of the poa.properties file (in the jar) are as follows:

dontDumpClasses = false
dontNormalize = false
count = false
useDeclaredTypes = false
verbose = false
#outDir = /tmp/out

Regards,
Manas

@ericbodden
Copy link
Member

There seems to be our problem… Can you try adding the transformations here:

transformations =
de.bodden.tamiflex.playout.transformation.clazz.ClassForNameTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassNewInstanceTransformation
de.bodden.tamiflex.playout.transformation.constructor.ConstructorNewInstanceTransformation
de.bodden.tamiflex.playout.transformation.method.MethodInvokeTransformation
de.bodden.tamiflex.playout.transformation.array.ArrayNewInstanceTransformation
de.bodden.tamiflex.playout.transformation.array.ArrayMultiNewInstanceTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetDeclaredFieldsTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetDeclaredFieldTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetDeclaredMethodsTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetDeclaredMethodTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetFieldTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetFieldsTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetMethodsTransformation
de.bodden.tamiflex.playout.transformation.clazz.ClassGetMethodTransformation
de.bodden.tamiflex.playout.transformation.constructor.ConstructorGetModifiersTransformation
de.bodden.tamiflex.playout.transformation.constructor.ConstructorToGenericStringTransformation
de.bodden.tamiflex.playout.transformation.constructor.ConstructorToStringTransformation
de.bodden.tamiflex.playout.transformation.field.FieldGetDeclaringClassTransformation
de.bodden.tamiflex.playout.transformation.field.FieldGetModifiersTransformation
de.bodden.tamiflex.playout.transformation.field.FieldGetNameTransformation
de.bodden.tamiflex.playout.transformation.field.FieldGetTransformation
de.bodden.tamiflex.playout.transformation.field.FieldSetTransformation
de.bodden.tamiflex.playout.transformation.field.FieldToGenericStringTransformation
de.bodden.tamiflex.playout.transformation.field.FieldToStringTransformation
de.bodden.tamiflex.playout.transformation.method.MethodGetDeclaringClassTransformation
de.bodden.tamiflex.playout.transformation.method.MethodGetModifiersTransformation
de.bodden.tamiflex.playout.transformation.method.MethodGetNameTransformation
de.bodden.tamiflex.playout.transformation.method.MethodToGenericStringTransformation
de.bodden.tamiflex.playout.transformation.method.MethodToStringTransformation

It’s odd, normally those should be configured by default.

Cheers
Eric

@manasthakur
Copy link
Author

Hi Eric,

I added the above properties to poa.properties, jarred it again, and am getting the log entries now (60 for avrora, 11708 for eclipse, etc.). I hope this is correct. Thanks.
Should the same be added to the version uploaded on the website?

Regards,
Manas

@ericbodden
Copy link
Member

There seems to be our problem… Can you try adding the transformations in the attached file?

It’s odd, normally those should be configured by default.

Cheers
Eric

On 26.10.2016, at 17:51, Denis Bogdanas [email protected] wrote:

Hi Eric,

The contents of the poa.properties file (in the jar) are as follows:

dontDumpClasses = false
dontNormalize = false
count = false
useDeclaredTypes = false
verbose = false
#outDir = /tmp/out

Regards,
Manas


You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

@manasthakur
Copy link
Author

Hi Eric,

I added the above properties to poa.properties, jarred it again, and am getting the log entries now (60 for avrora, 11708 for eclipse, etc.). I hope this is correct. Thanks.
However, it seems that many of the above transformations are not supported by Soot yet?

Regards,
Manas

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants