> Since nothing in the asm you dumped jumps to the > address Readdir+0x2d(SB) (0x0000b5d9-0x0000b5ac), > that tells me that whatever is broken, it's likely > not in this function.
Aha, thanks for the explanation. > At this point, this is really sounding like a hardware issue I also start to believe that, but not due to overheating. I did a proper installation of the components (e.g. thermal paste), The temps are normal. -marco > On 14.07.2024, at 03:06, o...@eigenstate.org wrote: > >> >> I am lost here. >> I read the acid manual, but I still don't know what this output is about. >> > > lstk() prints a stack trace -- or at least tries to, > but fails. That implies to me that your stack frame > is busted. > > asm()/casm() shows assembly. The PC you crashed on > is 0x0000b5d9, which happens to be in the middle of > this comparison instruction: > >> Readdir+0x2c 0x0000b5d8 CMPL dir+0x8(SB)(CX*1),AX >> Readdir+0x33 0x0000b5df JNE Readdir+0xd8(SB) > > which tells me whatever jumped into the code here > is junk; either a bad function pointer, a flipped > bit in your binary, or something else. > > Since nothing in the asm you dumped jumps to the > address Readdir+0x2d(SB) (0x0000b5d9-0x0000b5ac), > that tells me that whatever is broken, it's likely > not in this function. > ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/T68f44cf88ca61ff3-M0b7f14e11ca4ef4c445e5ad3 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
