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

Running a ! command in jdmpview that throws an error provides few details #15889

Closed
kgibm opened this issue Sep 14, 2022 · 0 comments · Fixed by #15890
Closed

Running a ! command in jdmpview that throws an error provides few details #15889

kgibm opened this issue Sep 14, 2022 · 0 comments · Fixed by #15890

Comments

@kgibm
Copy link
Contributor

kgibm commented Sep 14, 2022

Java -version output

java -version
openjdk version "1.8.0_352-internal"
OpenJDK Runtime Environment (build 1.8.0_352-internal-_2022_09_14_18_38-b00)
Eclipse OpenJ9 VM (build master-430e01e, JRE 1.8.0 Linux amd64-64-Bit Compressed References 20220914_000000 (JIT enabled, AOT enabled)
OpenJ9   - 430e01e
OMR      - 38e2433
JCL      - 8e8d4d3 based on jdk8u352-b05)

Summary of problem

When a !-command throws an exception, com.ibm.j9ddr.tools.ddrinteractive.Context catches it and only prints the exception's message, which is not useful for some exceptions; for example:

Problem running command:
null

A java.util.logging.Logger trace specification can be configured to get the full exception but this can be very complicated in certain environments (in my example, Eclipse). Given that the main end-user of these diagnostic tools can be assumed to be technical, it would be nice to simply print the entire exception details, including its class and stack.

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

Successfully merging a pull request may close this issue.

3 participants