Hi, I believe you can compile build/X86/gem5.debug to have all the symbols available for debugging.
I'm not sure about the error, but generally, when debugging an instruction, I would try to find the internal name of the instruction in gem5, and look at gem5/build/X86/arch/x86/arch/generated/ to find the implementation of the instruction. Regarding the unimplemented initiateAcc error, there are a few places to look at, - You can take a breakpoint when that instruction is decoded and find gem5's internal name for that instruction (e.g., MOV_M_R or MOV_R_M). - You can find how that instruction is decoded in gem5/build/X86/arch/x86/generated/decode-method.cc.inc. It's probably decoded into micro-op(s). - gem5/src/arch/x86/isa/insts/general_purpose/data_transfer/move.py seems to have the micro codes for move instructions. - You can use that name to find the ::execute() function, as well as ::initiateAcc() function of the micro-ops in gem5/build/X86/arch/x86/generated/exec-ns.cc.inc. Regards, Hoa Nguyen On Tue, Jan 3, 2023 at 7:07 PM Eliot Moss via gem5-users < gem5-users@gem5.org> wrote: > Dear gem5-ers -- Does this issue sound familiar? Could it be a bug > that's been fixed and that I get because I'm running with an older > version of gem5? (Apparently 21.0.0.0.) > > The failing instruction seems to be (x86 64): > > mov 0x283a8a(rip),rax > > which occurs in function _dl_catch_error in glibc 6. > > The bytes of that instruction are (in hex): 48 8b 05 8a 3a 28 00 > Exec debug flag printing of the instruction shows it decoded properly. > So how could its initiateAcc function be zapped? > > Btw, when diving into this sort of thing with gdb (debugging gem5, > not the program being simulated), I have not been able to find a way > to get at DynInstPtr referents when in gdb. Is there a trick to > printing / accessing fields of DynInst and StaticInst instances via > their respective Ptr types? The * and -> operator seem to be > unknown to gdb on those Ptr types. > > Regards - Eliot Moss > _______________________________________________ > gem5-users mailing list -- gem5-users@gem5.org > To unsubscribe send an email to gem5-users-le...@gem5.org >
_______________________________________________ gem5-users mailing list -- gem5-users@gem5.org To unsubscribe send an email to gem5-users-le...@gem5.org
