I will attach a test program in a minute to demonstrate - on x86_64, loading this program into the source window, and then attempting to read information from the start_thread frame (which shows up as the second [unknown] frame in the second thread) reliably prints out ptrace errors each time the frame is clicked, resulting in no information in the window. ptrace: Input/output error (pt 0x2, pid 11167, addr 0x555555998540, data 0x0) at frysk.sys.Ptrace$AddressSpace.peek(FryskGui) at frysk.proc.ptrace.AddressSpaceByteBuffer$PeekRequest.execute(FryskGui) at frysk.event.Request$Handler.execute(FryskGui) at frysk.event.EventLoop.runEventLoop(FryskGui) at frysk.event.EventLoop.run(FryskGui) at frysk.gui.Gui$4.run(FryskGui) at java.lang.Thread.run(libgcj.so.7rh)
Created attachment 1891 [details] gcc -g -O0 -o tester2 -lpthread tester2.c
I should mention this is FC6
Fixed.