-
Notifications
You must be signed in to change notification settings - Fork 737
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
Unexpected trace option processing with none and multiple components #20175
Comments
This wouldn't be a trivial change - the tool is very much built around the generation of a single option. The behaviour you describe (i.e. the JVM expanding the single option into two options, and
This can certainly be fixed. |
The list of tracepoint components in the Xtrace Option Builder is based on the list provided here: https://eclipse.dev/openj9/docs/xtrace/#tracepoint-specification If that list can be brought up to date I will include the new components in the tool. In addition to the missing OMR components, there are a number of components in J9TraceFormat.dat which look like they might need to be added too:
|
Created eclipse-openj9/openj9-docs#1413 |
@paulcheeseman there were more changes to eclipse-openj9/openj9-docs#1413 to add many more missing groups. |
The option
-Xtrace:none,maximal={omrport.220-223,j9jcl.156-161},output=shared%p.trc
gets parsed as the following, which isn't what is expected.The expected behavior requires
-Xtrace:none -Xtrace:maximal={omrport.220-223,j9jcl.156-161},output=shared%p.trc
Not sure if this is by design. It seems the -Xtrace option builder should be updated to specify
none
as a separate option.https://eclipse.dev/openj9/tools/xtrace_option_builder.html
Also, the list of trace components in the tool isn't complete, i.e. it doesn't include
omrport
, or any other omr trace components (omrutil, omrvm, omrti, omrmm - see OMRTraceFormat.dat).@keithc-ca @paulcheeseman
The text was updated successfully, but these errors were encountered: