log in | register | forums


User accounts
Register new account
Forgot password
Forum stats
List of members
Search the forums

Advanced search
Recent discussions
- CashBook and other goodies (News:)
- June News Round-up (News:)
- Getting started with Bash on RISC OS (News:1)
- !Organizer updated to 2.28a (News:)
- Geminus (Gen:8)
- A new monitor for my RISC OS and Mac systems (News:1)
- May news round-up (News:)
- How likely is it that... (PP:2)
- NetSurf or Iconbar? (Site:1)
- GDPR and RISC OS (News:1)
Latest postings RSS Feeds
RSS 2.0 | 1.0 | 0.9
Atom 0.3
Misc RDF | CDF
Site Search
Article archives
The Icon Bar: Programming: Corrupt heap
  Corrupt heap
  (14:57 28/4/2001)
  monkeyson (15:15 29/4/2001)
    Phlamethrower (11:23 30/4/2001)
Phlamethrower Message #4763, posted at 14:57, 28/4/2001
Unregistered user When this program is compiled and run with GCC, it complains of a corrupt heap:

#include <stdio.h>
#include <stdlib.h>

class foo
int blah;
foo() {printf("foo at %d\n",(int) this);}
~foo() {printf("foo killed at %d\n",(int) this);}

void main()
poo *t;
t = new foo[10];
delete t;

Basically what I want to know is whether this is a bug in GCC, a limit of C++, or that I've done something wrong somewhere.

  ^[ Log in to reply ]
monkeyson Message #4764, posted at 15:15, 29/4/2001, in reply to message #4763
Unregistered user s/poo/foo

I got a seg fault from Linux. Platform independence!

You need to alter the delete so that you're deleting an array of foos, not an individual foo.

foo *t;
t = new foo();
delete t;

foo *t;
t = new foo[10];
delete [ ] t;

  ^[ Log in to reply ]
Phlamethrower Message #4765, posted at 11:23, 30/4/2001, in reply to message #4764
Unregistered user Ah, right. I think I tried delete t[], but not delete []t.
  ^[ Log in to reply ]

The Icon Bar: Programming: Corrupt heap