Hi Shawn,
I think you are having issues with pipe. Instead of piping stdout and
stderr to head, you can redirect them ("--redirect-stdout" or "-r" for
stdout, and "--redirect-stderr" or "-e" for stderr) to a text file. Try
something like:
"'build/X86/gem5.opt --debug-flags=DRAM -e -r
configs/learning_gem5/part1/simple.py"
This would redirect stdout/stderr to your output directory, which by
default is m5out.
In general "build/X86/gem5.opt --help" would be helpful.
Best,
On Mon, May 11, 2020 at 12:13 AM Shawn via gem5-users <[email protected]>
wrote:
> Hello,
>
> I am a beginner of gem5. I am currently trying to learn how to debug in
> gem5.
>
> I read the introduction about debugging (
> https://www.gem5.org/documentation/learning_gem5/part2/debugging/) and
> tried 'build/X86/gem5.opt --debug-flags=DRAM
> configs/learning_gem5/part1/simple.py | head -n 50'. It did provides part
> of the output to the console, but after a few lines it failed and said:
>
> '
> close failed in file object destructor:
> sys.excepthook is missing
> lost sys.stderr
> '
>
> What should I do if I want to see all output?
>
> Thank you very much.
>
> Shawn Liu_______________________________________________
> gem5-users mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
--
Pouya Fotouhi
PhD Candidate
Department of Electrical and Computer Engineering
University of California, Davis
_______________________________________________
gem5-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]
%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
