-
|
Compare to AGCT, StackWalker::walkVM() would always output fixed pattern of stack frames. When calling the java Reflection method(Method#invoke: .call_stub()L; These frames are the fixed pattern. Can we just unwind these frames but not to fill the frames, like the AGCT stack backtrace results. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 6 replies
-
|
With If you are not interested in such level of detail, use other stack walking modes ( |
Beta Was this translation helpful? Give feedback.
-
|
@apangin since you have the start and end addresses for the call stub for other reasons, what do you think about adding an option to terminate the unwind when hitting the call stub? In my experience, Java users don’t care about how the VM runs the Java program, and should focus on things they can control, i.e. most frames below the call stub. If this information is useful to specialist users, the option to unwind further should be available. |
Beta Was this translation helpful? Give feedback.
With
cstack=vm, async-profiler collects full stack trace of a thread, including all intermediate JVM frames. This is intentional. It was exactly the reason whyvmmode appeared - completeness was one of the main requirements from customers (see #795).If you are not interested in such level of detail, use other stack walking modes (
cstack=dwarfmay be a good option). Alternatively, you may post-process recordings to exclude frames you don't need.