Re: RFR: 8339307: jhsdb jstack could not trace FFM upcall frame [v3]

2024-09-06 Thread Chris Plummer
On Sat, 7 Sep 2024 01:48:39 GMT, Yasumasa Suenaga wrote: >> This PR is successor of #20789 . I got some comments in there, then I needed >> to fix in many pooints. And also I have to fix branch name to kick GHA >> automatically (#20789 is named with `pr/`, it meets the condition to skip >> GHA

Re: RFR: 8339307: jhsdb jstack could not trace FFM upcall frame [v3]

2024-09-06 Thread Yasumasa Suenaga
> This PR is successor of #20789 . I got some comments in there, then I needed > to fix in many pooints. And also I have to fix branch name to kick GHA > automatically (#20789 is named with `pr/`, it meets the condition to skip > GHA). Hence I've opened another PR for this JBS issue. > > This P

Re: RFR: 8339307: jhsdb jstack could not trace FFM upcall frame [v3]

2024-09-06 Thread Yasumasa Suenaga
On Fri, 6 Sep 2024 15:29:18 GMT, Jorn Vernee wrote: >> Yasumasa Suenaga has updated the pull request incrementally with one >> additional commit since the last revision: >> >> Remove blank lines > > Looks great! Thanks for implementing the JFA-based stack walking. > > Please wait for another

Re: RFR: 8339307: jhsdb jstack could not trace FFM upcall frame [v3]

2024-09-02 Thread Andrey Turbanov
On Sat, 31 Aug 2024 09:34:09 GMT, Yasumasa Suenaga 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/nativese

Re: RFR: 8339307: jhsdb jstack could not trace FFM upcall frame [v3]

2024-08-31 Thread Yasumasa Suenaga
> 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