RFR: 8339307: jhsdb jstack could not trace FFM upcall frame [v3]
Andrey Turbanov
aturbanov at openjdk.org
Mon Sep 2 07:53:26 UTC 2024
On Sat, 31 Aug 2024 09:34:09 GMT, Yasumasa Suenaga <ysuenaga at openjdk.org> wrote:
>> I attempted to check stack trace in the core generated by [SEGV example in upcall](https://github.com/YaSuenag/garakuta/blob/841452d9176dab1ddbb552009c180530eb81190b/NativeSEGV/ffm/upcall/src/main/java/com/yasuenag/garakuta/nativesegv/upcall/Main.java) with `jhsdb jstack`, however it failed with following exception.
>>
>>
>> Error occurred during stack walking:
>> java.lang.RuntimeException: Couldn't deduce type of CodeBlob @0x00007fa04c265990 for PC=0x00007fa04c265aa6
>> at jdk.hotspot.agent/sun.jvm.hotspot.code.CodeCache.findBlobUnsafe(CodeCache.java:124)
>> at jdk.hotspot.agent/sun.jvm.hotspot.code.CodeCache.findBlob(CodeCache.java:83)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.Frame.cb(Frame.java:119)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.x86.X86Frame.adjustUnextendedSP(X86Frame.java:334)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.x86.X86Frame.initFrame(X86Frame.java:137)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.x86.X86Frame.<init>(X86Frame.java:163)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.x86.X86Frame.senderForInterpreterFrame(X86Frame.java:361)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.x86.X86Frame.sender(X86Frame.java:281)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.Frame.sender(Frame.java:207)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.Frame.realSender(Frame.java:212)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.VFrame.sender(VFrame.java:120)
>> at jdk.hotspot.agent/sun.jvm.hotspot.runtime.VFrame.javaSender(VFrame.java:144)
>> at jdk.hotspot.agent/sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:81)
>> at jdk.hotspot.agent/sun.jvm.hotspot.tools.StackTrace.run(StackTrace.java:45)
>> at jdk.hotspot.agent/sun.jvm.hotspot.tools.JStack.run(JStack.java:67)
>> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.startInternal(Tool.java:278)
>> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.start(Tool.java:241)
>> at jdk.hotspot.agent/sun.jvm.hotspot.tools.Tool.execute(Tool.java:134)
>> at jdk.hotspot.agent/sun.jvm.hotspot.tools.JStack.runWithArgs(JStack.java:90)
>> at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.runJSTACK(SALauncher.java:302)
>> at jdk.hotspot.agent/sun.jvm.hotspot.SALauncher.main(SALauncher.java:500)
>> Caused by: sun.jvm.hotspot.types.WrongTypeException: No suitable match for type of address 0x00007fa04c265990 (nearest symbol is _ZTV10Upcall...
>
> Yasumasa Suenaga has updated the pull request incrementally with one additional commit since the last revision:
>
> Add frame size to all of UpcallStub::create() call
test/hotspot/jtreg/serviceability/sa/LingeredAppWithFFMUpcall.java line 45:
> 43: try {
> 44: Thread.sleep(600000); // 10 min
> 45: } catch(InterruptedException e) {
Suggestion:
} catch (InterruptedException e) {
test/hotspot/jtreg/serviceability/sa/LingeredAppWithFFMUpcall.java line 61:
> 59:
> 60: public static void main(String[] args) {
> 61: try{
Suggestion:
try {
test/hotspot/jtreg/serviceability/sa/LingeredAppWithFFMUpcall.java line 65:
> 63: (new Thread(() -> callJNI(upcallAddr), THREAD_NAME)).start();
> 64: LingeredApp.main(args);
> 65: } catch(Exception e) {
Suggestion:
} catch (Exception e) {
-------------
PR Review Comment: https://git.openjdk.org/jdk/pull/20789#discussion_r1740474940
PR Review Comment: https://git.openjdk.org/jdk/pull/20789#discussion_r1740475126
PR Review Comment: https://git.openjdk.org/jdk/pull/20789#discussion_r1740475258
More information about the serviceability-dev
mailing list