This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB 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] |
Hello, Just FYI, in case others may feel the same way? We have now run this test pretty much on most of our Unix native platforms, and have found that the bigcore.exp testcase is usually quite stressful for the host where the testing is being conducted. For instance, on sparc-solaris, the system ran out of virtual memory and swap space, and started killing processes at random. It also requires a very large amount of disk space to be available for the core file (2GB on x86-linux). So I was told by other fellow machine users to please stop running this test on our build machines. One thing I would recommend is to delete the core file once the test is finished. I had a testsuite run that got ruined because the core file filled up all my disk, and left no space available for the rest of the run... 2004-03-12 J. Brobecker <brobecker@gnat.com> * gdb.base/bigcore.exp: Delete core file after test has completed. Sounds reasonable? -- Joel
Attachment:
bigcore.exp
Description: Text document
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |