On 7/15/07, Ludovic Brenta <[EMAIL PROTECTED]> wrote:
I crudely measured, using top(1) and a sampling period of 0.5 s, that g++ uses as much as 474 Mb of virtual memory when compiling the largest file in monotone (revision.cc). That might explain why g++ seems to have run out of memory on two different arm machines, smackdown and cats.
I don't think this is out of memory, I think this is a real compiler bug. The crash is in the same place for both failed builds: database_check.cc: In function 'void report_certs(const std::map<revision<hexenc<id> >, checked_revision, std::less<revision<hexenc<id> > >, std::allocator<std::pair<const revision<hexenc<id> >, checked_revision> > >&, size_t&, size_t&, size_t&, size_t&)': database_check.cc:835: internal compiler error: Segmentation fault The function in question is not terribly complicated - and compilation of several more complicated functions/files has already succeeded at the point where the buildd failed. zw -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
