https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #27 from Martin Jambor <jamborm at gcc dot gnu.org> --- Created attachment 41517 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41517&action=edit Hack for revealing compiler command lines Thanks Ian, the above was definitely helpful but did not allow me to get at the compiler invocation lines, which was what I needed to get at tree dumps, run the compilation in gdb and so forth. In the end, i had to resort to the attached hack to get them. I do not know how the trace feature of libgo/gotest script is supposed to work but I had to redirect them to find them. It would be great if the testsuite left some libgo.log file with all necessary command lines to replay the test by hand like all other testsuites do. I spent half of the time on this bug so far just looking for the command lines which does not look reasonable.