crash when run out of memory

[jy]

I have a C++ program which is "purify" clean, but crashes (called terminate)
when run out of memory on linux 2.4.27. From the core file, the crashes happen
after I throw an exception (after malloc returns null), and the stack winding
was calling the destructor of a large object. What's the genearl guidlines for
debugging, fixing, or at least making it a graceful exit than a crash?

Thanks,

-jy

[Artie Gold]

jy wrote:

I have a C++ program which is "purify" clean, but crashes (called terminate)
when run out of memory on linux 2.4.27. From the core file, the crashes happen
after I throw an exception (after malloc returns null), and the stack winding
was calling the destructor of a large object. What's the genearl guidlines for
debugging, fixing, or at least making it a graceful exit than a crash?

Thanks,

-jy

Without seeing your code it's impossible to be sure, but I suspect your
problem is platform specific (and due to overcommitment of memory in Linux).

[Followup-To set: news:comp.os.li nux.development .apps]

HTH,
--ag

--
Artie Gold -- Austin, Texas

http://it-matters.blogspot.com

[Karthik Kumar]

jy wrote:

I have a C++ program which is "purify" clean, but crashes (called terminate)
when run out of memory on linux 2.4.27. From the core file, the crashes happen
after I throw an exception (after malloc returns null),
Did you say it is a C++ . Why would you use malloc then ?
Why not new ?
and the stack winding
was calling the destructor of a large object.

Was that large object defined as local to the function ?
Post some code here.

--
Karthik. http://akktech.blogspot.com .
' Remove _nospamplz from my email to mail me. '

[Ali Çehreli]

"jy" <jy*******@yaho o.com> wrote in message
news:fa******** *************** ***@posting.goo gle.com...

I have a C++ program which is "purify" clean, but crashes (called terminate) when run out of memory on linux 2.4.27. From the core file, the crashes happen after I throw an exception (after malloc returns null),
I think it is new that throws the exception, not you. new is likely
using malloc internally and throwing std::bad_alloc when there is no
memory.
and the stack winding
was calling the destructor of a large object. What's the genearl guidlines for debugging, fixing, or at least making it a graceful exit than a crash?

Catch std::bad_alloc exception in main and report it:

int main()
{
try
{
/* the application code */
}
catch (std::bad_alloc const &)
{
cout << "no memory\n";
}
}

Ali