lable.
Maybe my SCons version is influencing things and forcing Python v3.6.8 somehow?
Cheers,
~Aaron Vose
-Original Message-
From: Aaron Vose
Sent: Tuesday, June 27, 2023 7:19 PM
To: Boris Shingarov ; The gem5 Users mailing list
Subject: RE: [gem5-users] Gem5 with pydot
Have you re
lsewhere? When I try the above code in a new
file called "test_pydot.py", I do see what I would expect: "!!avose: Have
PyDot!".
Thanks again,
~Aaron Vose
-Original Message-
From: Boris Shingarov
Sent: Monday, June 26, 2023 3:22 PM
To: The gem5 Users mailing list
Cc: Aar
I would debug it like this:
Near the beginning of dot_writer.py, there is:
try:
import pydot
except:
pydot = False
Replace the "pydot = False" with "import pdb; pdb.set_trace()".
This will drop you into a debug shell where you can investigate why
"import pydot" failed.
On 6/26/23
gem5.debug fs.py --kernel=riscv.elf --wait-gdb
On 6/15/23 22:17, wanghw364 via gem5-users wrote:
Hi,
Does gem5 riscv support remote gdb to debug the target riscv elf?
I tried in this way but riscv gdb can't connect gem5 and showed
connection time out and gem5 keep running the elf to the end:
Felipe,
What do `file` and `riscv-linux-gnu-objdump` (or whatever your
cross-toolchain calls objdump) say about `binario.riscv`? I don't know
where that "--interp-dir sysroot" in your output came from, but it
smells like we are dealing with dynamic-ELF here and I suggest you start
from the
I don't think O3 ever worked with PowerPC. We have plans to fix it some day (but this will not be soon).-"yangyuqing--- via gem5-users" wrote: -To: gem5-users@gem5.orgFrom: "yangyuqing--- via gem5-users" Date: 09/30/2021 02:06AMCc:
art () at demo.c:6
Obviously other debuggers work well with this, I gave the example of GDB
simply because that's standard reference, but the only limit here is
your imagination. I use my own custom debugger I wrote for my [admittedly
weird] needs (github://shingarov/SmallRSP if you are curious),
Liyichao,
In fact, our group have been using that change since at least 2014 and it holds
up in pretty complex debugging scenarios. I hope it will be merged soon. I
would be really interested to hear whether it will help in your scenario.
Boris
-"Gabe Black via gem5-users" wrote: -
> set architecture arm
That shouldn't be necessary.
When you do "target remote", gem5 sends an XML "features descriptor" to GDB;
this contains detailed information about the architecture (because just saying
"arm" is not enough). One thing I would try, is do
target remote localhost:7000
show
Muhammad,Do you mean debugging the guest, or debugging gem5 itself? I regularly do both, and it's been a very smooth, uncomplicated experience. You debug gem5 just like any C++ application; it will launch under local gdb control. Debugging the guest is slightly more involved, you need to set up
> The microcode ISA I used I got mostly from an AMD patent from the K6 I
> think, extrapolated
This is very interesting, I'd be eager to read that. Do you approximately
remember what terms were in the name of the patent, to search for? AMD owns
over eleven thousand patents...
Which ISA? What version of the compiler, and what version of libc?On PowerPC and MIPS, syscall support in GEM5 has lagged so far behind that GEM5 will crash on SE workloads linked to any reasonably-recent glibc.-"gem5-users" wrote: -To:
I thought Paul and I fixed this back in September.I'll investigate in more detail tomorrow.-"gem5-users" wrote: -To: gem5 users mailing list From: Ciro Santilli Sent by: "gem5-users"
Avais,I think the standard textbook is:Sorin, Hill, Wood: A Primer on Memory Consistency and Cache Coherence. Published by Morgan and Claypool.Boris-"gem5-users" wrote: -To: gem5 users mailing list From: Muhammad Avais
gem5-users mailing listgem5-users@gem5.orghttp://m5sim.org/cgi-bin/mailman/listinfo/gem5-users[attachment "remoteDebugFix.diff" removed by Boris Shingarov/Employee/LW-US]
___
gem5-users mailing list
gem5-users@gem5.org
http://m5sim.org/cgi-bin/mailman/listinfo/gem5-users
Hi Alec,This is hugely exciting!I think I would be interested in trying my compiler backend which I am attempting to write, with it, no matter how incomplete, because the backend really uses the most rudimentary instructions and those are themselves described in a sort of declarative DSL, so if an
Hi Murat,I recently used GEM5 for simulating MIPS. I'd say as it is right now, GEM5 has a number of issues which would prevent it from running an arbitrary MIPS executable, but for my own (very specific) project goals, GEM5 worked very well. I recently wrote about it in this list, you may want
Hemendra,How recent is your GEM5?This used to be a problem until I fixed it about a month ago.If you are using GEM5 older than that, then I suggest to try the current head in the Mercurial repository. If you are already using that and the problem is still happening, give me a shout and we will
Kany,Can you point an exact url to explain what is gprog? Google comes up with an AVR programmer board, a "big jet plane" etc. -"gem5-users" wrote: -To: gem5-users@gem5.orgFrom: Kany Sent by: "gem5-users" Date:
Tod,>Could you please point to, where exactly is>the part on "Instrumenting a Benchmark”?I think Andreas is talking about the video called "Common Tasks", towards the end. But I would recommend that you watch all of them -- at least I did find them highly instructive.Boris
Shortly after the beginning of _start(), the C library issues the uname() syscall to verify for the minimum kernel version.If you look at gem5/src/arch/arm/linux/process.cc, you will see that in 32-bit mode the emulated syscall returns "3.0.0" and in 64, "3.7.0+".When you configured the toolchain
Unfortunately, the problem is bigger than that (so a full rebuild won't
help).
The issue is due to a C++ ABI incompatibility between g++ versions. The
libprotobuf library binary installed with the distro, is compiled with gcc
that is so new (5.2.1 in my case of Ubuntu 5.10) that if you are
Ah, yes. That's a mess of g++ versions, library versions and incompatible C++ ABIs.The easy workaround, if you don't need tracing, would be to disable protobuf:export PROTOC=/bin/falsescons build/ARM/gem5.optWhat version of gcc are you running? (gcc -v)-"gem5-users"
Yes, MIPS SE syscall emulation definitely does not work.As a trivial experiment, one of the "known good examples" in crosstools-NG is "mipsel-unknown-linux-gnu". This is with gcc-5.1.0, linux-4.0.4, glibc-2.21.If you compile "Hello World" with this toolchain, its glibc will try to complain about
Guru Prasad wrote:I followed the instructions given here to debug simulated code.
I run into the following issue with gdb-7.8.1.(gdb) set remote Z-packet on(gdb) set tdesc filename features/arm-with-neon.xml(gdb) symbol-file linux-linaro-gem5/vmlinuxReading symbols from
25 matches
Mail list logo