First of all, I thank him for answering my question. However, as a Chinese, his
profile picture does not respect our country. If my behavior affects other
members of the community, I am sorry.
___
gem5-users mailing list -- gem5-users@gem5.org
To unsubs
Please speak to other members of our community with respect. Nobody owes
you help, and nobody is likely to volunteer it to someone with a bad
attitude. Don't send emails to both gem5-users and gem5-dev, gem5-users is
enough.
Gabe
On Thu, Oct 1, 2020 at 6:42 PM 1154063264--- via gem5-users <
gem5-
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.
Please change your avatar。
___
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
Please provide fuller reproduction details.
On Thu, Oct 1, 2020 at 8:39 AM 1154063264--- via gem5-users
wrote:
>
> I am trying to run parsec in MESI_Three_Level-gem5.opt for ARM architecture
> in FS mode, but I am getting a segmentation fault.
>
> info: Entering event queue @ 25592214185500. St
I am trying to run parsec in MESI_Three_Level-gem5.opt for ARM architecture in
FS mode, but I am getting a segmentation fault.
info: Entering event queue @ 25592214185500. Starting simulation...
info: Entering event queue @ 2559222830. Starting simulation...
gem5 has encountered a segmentat
