🚀 go-pugleaf

I ran into an strange behavior is the new handler of g++. When I step into
G++'s new handler whenever I'm doing 'new char[x]', or something, I see
a very large bogus number passed.  With gdb I see:

0xab6fd8 in __builtin_new (sz=269806064) at ./libgcc2.c:1

This is on an SGI Indigo 2 with Irix 5.3. The same happens on a DEC alpha,
and sometimes bombs with a 'virtual memory exceeded'.

I tried to create my own new handler like this:

extern void * operator new (size_t size)
{
  void *p;
  p = malloc (size);
  if (p == 0)
  { cerr << "Memory exhausted; check swap space.\n";
    abort();
  }
  return p;
}

This bombs immediately, and size is very large.

I'm using G++ 2.7.2 on both the SGI and DEC alpha. Is this a gcc bug?

Any help appreciated,
Koert

--
Koert Zeilstra
Work: kzeil@comsearch.com  --  Home: koert@zen.cais.com 
Just my thoughts, not anyone else's.