Hi Community, I ran into bad_alloc issues in GEM5 with the full system simulation of SPEC 2006 benchmarks. Suspecting a memory leak, I wanted to use valgrind to understand better.
Without valgrind option, it takes less than 10 minutes for kernel to boot and also run the 400.perlbench/attrs benchmark. But with valgrind, it has crossed 2 hrs and the kernel hasn't yet booted. Usage: valgrind --log-file=attrs.val.txt --error-limit=no $GEM5_CMD I would like to know if this slowdown is reasonable with valgrind? And do you have any suggestions for a memory leak detection tool that is faster than valgrind and works well with gem5? Appreciate your time and effort. Thanks much. Best Regards Sindhuja
_______________________________________________ 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
