Re: new () keeps core-dump instead of generating exception
On Mar 6, 8:00 pm, "wenm...@yahoo.com" <wenm...@yahoo.com> wrote:
I am trying to allocate some objects during application starts up. The
objects are created through new operator, but for some reason, the
application keeps crashing and here is the debug trace:
(gdb) where
#0 0xb64349dd in _int_malloc () from /lib/tls/libc.so.6
#1 0xb6433ced in malloc () from /lib/tls/libc.so.6
#2 0xb659789e in operator new () from /usr/lib/libstdc++.so.5
I am using redhat Linux 2.4.21-15.ELsm, any idea why is that?
Any idea as to why you're using redhat Linux, no.
If you meant why you're crashing, it's impossible to say, but in
general, supposing that you've linked in the right versions of
everything, it's probable that you've mucked up the free store
arena with some illegal memory writes earlier. (Or, as someone
else suggested, you've requested more memory than is available,
and aren't catching the exception---and possibly cannot catch
it, if you're still running static initializers.)
--
James Kanze (GABI Software) email:james.kanze@gmail.com
Conseils en informatique orient=E9e objet/
Beratung in objektorientierter Datenverarbeitung
9 place S=E9mard, 78210 St.-Cyr-l'=C9cole, France, +33 (0)1 30 23 00 34