RFR: 8304725: AsyncGetCallTrace can cause SIGBUS on M1 [v3]
Thomas Stuefe
stuefe at openjdk.org
Thu Mar 23 12:48:12 UTC 2023
On Thu, 23 Mar 2023 12:00:33 GMT, Johannes Bechberger <jbechberger at openjdk.org> wrote:
> > In particular, we do not know if AGCT did interrupt the crashing thread recently. Or do we? This would be valuable information.
>
> Yes. But it could indeed be helpful information when debugging problems. Please don't forget that JFR has a very similar code, and it would be good to have the information on whether JFR sampled a thread recently too.
Yes, but while JFR interrupts threads too, its sampler runs in its own thread, so the async-safety of the interrupted code should not matter, or?
wrt info, just a little marker in the thread "AGCT was here", maybe with a timestamp, would be useful.
-------------
PR Comment: https://git.openjdk.org/jdk/pull/13144#issuecomment-1481130844
More information about the hotspot-dev
mailing list