Why debugging with gdb is so hard in gem5? I have worked with some other programs that are more gdb friendly than gem5. For example, in Flexus, if -gdb is passed to the command line, a PID is given to the user so that he can attach gdb to that PID. Then when ever a segmentation fault occurs, the gdb catches the signal and the user can view the backtrace. It is easy to find whcih function caused that fault (for example pointer and array faults).
I got a seg fault and till now I have not located where in the code, the fault occurs. I have read the documentation about debugging. Tracing the assembly code is not suitable for my case. -- // Naderan *Mahmood; _______________________________________________ gem5-users mailing list [email protected] http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
