This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug go/83794] misc/cgo/test uses gigabytes of memory


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83794

Ian Lance Taylor <ian at airs dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED

--- Comment #4 from Ian Lance Taylor <ian at airs dot com> ---
Thanks for investigating.  I fixed the problem you found in TestBuildID.  The
logs generated by t.Logf are saved until the test is complete, because tests
can run in parallel and interleaved logs are hard to read.  So 1) that explains
why you didn't see any of the logs; 2) it explains why the program allocated
memory very quickly and without bound.

Let me know if you still see a problem with `make check-gotools` after that
patch.  I don't know if there is anything else going on.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]