> > <mailto:
niketa@xxxxxxxxxxxxx <mailto:
niketa@xxxxxxxxxxxxx>>> wrote:
> >
> > The memory in your host machine is getting all used up and
> nothing
> > else
> > is getting allocated memory.
> >
> > It might be because you are running other memory intensive
> > processes or
> > your host system memory size is too low.
> >
> > Niket
> >
> > Zhang Yu wrote:
> > > Hi,
> > >
> > > I was trying to run a 64-core simulation, but when I load
> ruby, the
> > > simulation just stopped and I got these information:
> > >
> > > Processors: 64
> > > *** Simics getting shaky, switching to 'safe' mode.
> > > *** Simics (main thread) received an abort signal,
> probably an
> > assertion.
> > > Starting command line. (May have skipped commands in
> script files.)
> > > *** [VTMEM] At
> /home/mp/simics-2.2.19/src/core/util/strbuf.c:80,
> > > allocating cha
> > > r (1 byte each):
> > > .......
> > >
> > > terminate called after throwing an instance of
> 'std::bad_alloc'
> > > what(): St9bad_alloc
> > > fork failed: Cannot allocate memory
> > >
> > > Is this because the memory size I set in simics is too
> low? But
> > I have
> > > no problem if I don't load ruby. What should I do to solve
> this
> > problem?
> > >
> > > Thanks,
> > > Yu
> > >
> >
> ------------------------------------------------------------------------
> > >
> > > _______________________________________________
> > > Gems-users mailing list
> > >
Gems-users@xxxxxxxxxxx <mailto:
Gems-users@xxxxxxxxxxx>