Date: Thu, 31 Oct 2024 13:42:19 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 282445] Wrong stack() info in dtrace Message-ID: <bug-282445-227-qNddpXVWnb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-282445-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=282445 Artem Hevorhian <artemhevorhian@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Open |Closed Resolution|--- |Works As Intended --- Comment #2 from Artem Hevorhian <artemhevorhian@gmail.com> --- Well, > I see that the instruction in each case is the instruction *after* the call instruction which leads to the next frame in the stack, which is an artifact of the way stack unwinding is handled. It explains everything. I see exactly the same behavior on my machine. This ticket could be closed now. Everything works as expected. >> Because the pure hash value seems to be okay. > What do you mean by this? After looking closely, I see that here the instruction points correctly at jmp, which one instruction after the one being currently tracked. Correct. I think this ticket can be closed now. Thank you very much for the explanation. Have a good day! -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-282445-227-qNddpXVWnb>