My three big deadlines are all over tomorrow. I'd like us to spend
some time this week to get everything all set to release the
repository. This job is mostly for myself and Gabe, but we need to
answer various questions about mailing list archives and such as well.
Nate
I believe all the FAILEDs below are just the long runs whose stats didn't
get updated after my cache changes. I can't tell what happened on the last
one (the Error 3), so I'm hypothesizing that it was just a pool glitch and
I'm rerunning now.
Steve
On Sun, Mar 16, 2008 at 8:10 AM, Cron Daemon
Funny, I got this error:
system.cpu7: completed 630 read accesses @9833512177
system.cpu5: completed 630 read accesses @9838116814
terminate called after throwing an instance of 'std::bad_alloc'
what(): St9bad_alloc
Program aborted at cycle 9948602663
I've never even seen that
Generally, yes. Memory leak?
2008/3/16 Steve Reinhardt [EMAIL PROTECTED]:
Funny, I got this error:
system.cpu7: completed 630 read accesses @9833512177
system.cpu5: completed 630 read accesses @9838116814
terminate called after throwing an instance of 'std::bad_alloc'
what():
looks like it...
On Sun, Mar 16, 2008 at 11:37 AM, nathan binkert [EMAIL PROTECTED] wrote:
Generally, yes. Memory leak?
2008/3/16 Steve Reinhardt [EMAIL PROTECTED]:
Funny, I got this error:
system.cpu7: completed 630 read accesses @9833512177
system.cpu5: completed 630 read
Surprisingly, it looks like the RTC provided as part of the CMOS
(don't ask me why) is exactly the same as the one provided by the
tsunami io chip. I'd like to split that out into a separate device or at
least a class that I can just use rather than redoing it all. Also, it
uses #define for