-
Notifications
You must be signed in to change notification settings - Fork 959
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
Stack map does not match the one at exception handler #560
Comments
Hi, thanks for reporting this! TBH, the type descriptor |
The source code of the BTraceTest class:
The source code of the trace script:
There are also three warnings output at console, full log as follow:
|
Unfortunately, even this reproducer does not reproduce for me. I tried BTrace 2.2.2 as well as trunk build they all work fine. Here is my env, for comparison. The only difference I see is that I am using JDK 17.0.3.1 whereas you are using 17.0.3 - but AFAICT from the JDK release notes this difference should not affect anything.
Could you run this command on the trunk build of BTrace and attach here the file you should find at
|
It very strange, I now can successfully trace with command: But BTrace plugin in VisualVM can still reproduce this issue. VisualVM's version is : I Start it with command: BTrace plugin's version is:
Here is the |
Well, in VisualVM is still version 2.1.0 which is rather old (working on getting the current version to VisualVM UC soon with the maintainers - but in the meantime you can download the updated plugins from https://github.com/btraceio/btrace.visualvm/releases/tag/v2.2.2 and install them manually). The generated probe class from the archive you sent looks fine (as expected). If the problem is not reproducible in BTrace 2.2.2 or the trunk build I would close this issue. The 2.1.0 version is pretty outdated and there will be no updates to 2.1.* line. |
Plugin from https://github.com/btraceio/btrace.visualvm/releases/tag/v2.2.2 can reproduce this issue. First I uninstall, then restart VisualVM to reinstall. I think this can remove previous version plugin's effect. I realize plugin's version 2.1.0 which is BTrace Workbench's version , its base on BTrace API 2.2.0. I think previous installed plugin already is version 2.2.0. I also did some other experiments, after btrace plugin cause this issue, I rerun the program from eclipse, then try to trace, |
Stale issue message |
Hi,
I'm facing an issue when try to use btrace, it seems can't get some valuable clue from google.
Software versions as follow:
The text was updated successfully, but these errors were encountered: