The "hack" line is basically letting you know about something that
should work but isn't done in the best way, aka a hack, in the M5
code. I've seen that particular hack message many times, and I doubt
it's related to your problem.
The first thing you should do if you're using the stable repository is
to upgrade to the development one. I mention that because of the path
in your output, and if you're already using the development one then
don't worry about it. The stable repository is quite old and has a lot
of bugs that have been fixed in the development repository. There's
really no advantage to using it.
The second thing you should try is to run m5.opt instead of m5.fast.
m5.fast is marginally faster than m5.opt because it compiles out all
the asserts, tracing, etc., that's used for debugging. If you use
m5.opt you might hit an assert that will give you more information
about what's happening.
Third, if you're still having trouble with this segfault, run m5.opt
or even better m5.debug (which will be a bit slower but is for this
sort of thing) under gdb. When it hits the segfault or assert, use the
bt command to get a backtrace to see what it was trying to do and to
what.
Gabe
Quoting Veydan Wu <[email protected]>:
Hi, all, I am using M5 ALPHA FS mode. There is a strange runtime error:
*M5 compiled Nov 12 2010 22:40:32
M5 revision Unknown
M5 started Nov 12 2010 22:43:25
M5 executing on ubuntu
command line: build/ALPHA_FS/m5.fast configs/example/fs.py -n 1 --caches
--l2cache
Global frequency set at 1000000000000 ticks per second
info: kernel located at:
/media/Study/CPU/CPUsource/M5/m5-stable-94c016415053/dist/m5/system/binaries/vmlinux
Listening for system connection on port 3456
0: system.remote_gdb.listener: listening for remote gdb on port 7000
**** REAL SIMULATION ****
info: Entering event queue @ 0. Starting simulation...
hack: be nice to actually delete the event here
Writing checkpoint
info: Entering event queue @ 1827283634500. Starting simulation...
7789 Segmentation fault build/ALPHA_FS/m5.fast configs/example/fs.py -n
1 --caches --l2cache*
I modified the rcS file in the disk image file, I only added:
/sbin/m5 checkpoint
/sbin/m5 dumpstats
/sbin/m5 resetstats
./my_program
Can someone tell me what the line "hack:..." mean? Thanks.
--
Regards,
Weidan Wu
_______________________________________________
m5-users mailing list
[email protected]
http://m5sim.org/cgi-bin/mailman/listinfo/m5-users
