Hi Yuan,
I use it all the time to see where my implementation is failing, the way
you can do it is
1. Compile gem5 in debug mode (you can do opt too but I prefer debug)
2. Run the application with gdb - - args (gem5 cli command)
3. Then run the application(type “r”)
4. Type “bt” to perform backtr
Hi, Abhishek,
Thanks for your help. Do you have any hints about gdb backtrace in gem5? I
am new to gdb debugging.
Best regards.
On Fri, Oct 2, 2020 at 12:03 PM Abhishek Singh <
abhishek.singh199...@gmail.com> wrote:
> Hi Yuan,
>
> Can you just backtrace using gdb, this will directly point the g
Hi Yuan,
Can you just backtrace using gdb, this will directly point the gem5
function which is giving the error?
On Fri, Oct 2, 2020 at 12:01 PM Shougang Yuan via gem5-users <
gem5-users@gem5.org> wrote:
> Hi, Giacomo,
>
> Thanks for your help. I am currently suffering a new problem. I set the
>
Hi, Giacomo,
Thanks for your help. I am currently suffering a new problem. I set the
break tick to be a relatively large number because the segmentation faults
in my simulation happen after several millions of instructions, and the gdb
has run the whole night up to now but it still can not reach t
Hi Shougang
curTick is a function as you can see from:
(gdb) p curTick
$1 = {Tick (void)} 0x562aea48
Could you try doing:
(gdb) p curTick()
It should display the current Tick time
Giacomo
From: Shougang Yuan via gem5-users
Sent: 02 October 2020 04:00
To: gem5 users mailing list
Cc: Sh
