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 the tick I
want to look at. So do you know how to jump to the interesting program
phase more quickly?
Best regards.
Shougang
On Fri, Oct 2, 2020 at 5:49 AM Giacomo Travaglini <
giacomo.travagl...@arm.com> wrote:
> Hi Shougang
>
>
>
> curTick is a function as you can see from:
>
>
>
> (gdb) p curTick
> $1 = {Tick (void)} 0x5555562aea48 <curTick()>
>
>
>
> Could you try doing:
>
>
>
> (gdb) p curTick()
>
>
>
> It should display the current Tick time
>
>
>
> Giacomo
>
>
>
> *From:* Shougang Yuan via gem5-users <gem5-users@gem5.org>
> *Sent:* 02 October 2020 04:00
> *To:* gem5 users mailing list <gem5-users@gem5.org>
> *Cc:* Shougang Yuan <syu...@ncsu.edu>
> *Subject:* [gem5-users] GDB debug help
>
>
>
> Hi, All,
>
>
>
> I am running simulation in se mode and trying to use gdb debug a
> segmentation fault. Through trace debug, I found that the simulation
> suffers a segmentation fault in tick 534558604750.
>
>
>
> To figure out the reason for this bug, I launched the gdb debugger. But I
> suffered some weird results. Usually, when using gdb debug, we use
> "--debug-break" or "schedBrak()" to set breakpoint. And we can use "p
> curTick" to dump out the current tick.
>
>
>
> My simulation stopped at tick 534558604750, and I sched the break in tick
> 1000000. It is much more early than the time when this memory bug happens.
> But when I call "p curTick", the gdb dumped out something like the
> following:
>
>
>
> Program received signal SIGTRAP, Trace/breakpoint trap.
> 0x00007ffff5c28237 in kill () at ../sysdeps/unix/syscall-template.S:78
> 78 ../sysdeps/unix/syscall-template.S: No such file or directory.
> (gdb) p curTick
> $1 = {Tick (void)} 0x5555562aea48 <curTick()>
> (gdb) p _curTick
> No symbol "_curTick" in current context.
> (gdb)
>
>
>
> And when I set the breakpoint time to tick 2000, this is the very
> beginning of the simulation, I still can not dump out the current tick
> value.
>
>
>
> So what's wrong with it? Can some please help me out? Thanks for your help.
>
>
>
> Best regards.
>
> Yuan
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
>
_______________________________________________
gem5-users mailing list -- gem5-users@gem5.org
To unsubscribe send an email to gem5-users-le...@gem5.org
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
