RFR: 8359366: RunThese30M.java EXCEPTION_ACCESS_VIOLATION in JvmtiBreakpoints::clearall_in_class_at_safepoint
Leonid Mesnik
lmesnik at openjdk.org
Mon Jun 30 21:15:40 UTC 2025
On Mon, 30 Jun 2025 20:47:35 GMT, Serguei Spitsyn <sspitsyn at openjdk.org> wrote:
> The issue itself is kind of artificial. The debugger should not set breakpoints concurrently with class redefinitions. But suppose this can really happen. Then I have a little preference to fix this by setting a breakpoint after redefinition when it is possible.
That might happens if the another javaagent request retransformation independently from debugger agent. It indeed quite rare but might happens.
I planned to change the fix to use methodHandle instead of jmehtodid. However it means that it is needed to reconstruct breakpoint with new method. I think it is too complicated and can't be well tested.
Let me publish the second approach to decide what would be better to do with breakpoint.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/26031#issuecomment-3020763227
More information about the hotspot-dev
mailing list