https://sourceware.org/bugzilla/show_bug.cgi?id=21174
--- Comment #7 from Thommy Jakobsson ---
Created attachment 9834
--> https://sourceware.org/bugzilla/attachment.cgi?id=9834&action=edit
Add debug printouts in the perf stack unwind
--
You are receiving this mail because:
You are on the CC
https://sourceware.org/bugzilla/show_bug.cgi?id=21174
--- Comment #6 from Thommy Jakobsson ---
Hi again and thanks for spending the time.
>>Maybe you can debug by triggering the pr_debug ()
Switched the pr_debug to a normal printf, and also added a printout of program
counter directly in the lib
https://sourceware.org/bugzilla/show_bug.cgi?id=21174
--- Comment #5 from Mark Wielaard ---
(In reply to Thommy Jakobsson from comment #3)
> (In reply to Mark Wielaard from comment #1)
> > How does perf call the libdw getframe function?
> The actual call looks like this
> err = dwfl_getthread_fra
https://sourceware.org/bugzilla/show_bug.cgi?id=21174
--- Comment #4 from Mark Wielaard ---
(In reply to Thommy Jakobsson from comment #2)
> Created attachment 9833 [details]
> disassembly of function IBUFDIST_distribute
That shows the (duplicated) address 6e3628 is the last one before the retur
https://sourceware.org/bugzilla/show_bug.cgi?id=21174
--- Comment #3 from Thommy Jakobsson ---
(In reply to Mark Wielaard from comment #1)
> There is no good way to tell. It could happen if the function calls itself
> (although you would expect the pc to be different).
I did check the assembler
https://sourceware.org/bugzilla/show_bug.cgi?id=21174
--- Comment #2 from Thommy Jakobsson ---
Created attachment 9833
--> https://sourceware.org/bugzilla/attachment.cgi?id=9833&action=edit
disassembly of function IBUFDIST_distribute
--
You are receiving this mail because:
You are on the CC l
https://sourceware.org/bugzilla/show_bug.cgi?id=21174
Mark Wielaard changed:
What|Removed |Added
CC||mark at klomp dot org
--- Comment #1