freeing the memory using delete for a class object created using new gives exception.

Question

1.00/5 (1 vote)

See more:

freeing the memory using delete for a class object created using new gives exception.
The class is

C++

class CSnp : public CObject
{
    public:
        CSnp();
        ~CSnp();
        char liststr[50];
        char sSnpDesc[50];
        CTime tDateTime;
        int iDCSSerialKey;        
 };

Posted 23-Aug-11 1:51am

manoharbalu

Updated 23-Aug-11 2:05am

Stefan_Lang

v2

Add a Solution

Comments

CPallini 23-Aug-11 7:57am

Please dont cross-post. And please provide implementation code.

Philippe Mori 23-Aug-11 8:00am

Uses code block for you code and provide useful code if you want any help.

3 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

barneyman · Answer 1 · 2011-08-23T01:59:00

Solution 1

an exception on delete normally means you've exceeded the bounds of the allocation during use ... i'd look at the use of

C++

liststr

and

C++

sSnpDesc

at runtime

Posted 23-Aug-11 1:59am

barneyman

Philippe Mori · Answer 2 · 2011-08-23T02:01:00

Solution 2

Put a breakpoint in your destructor. The main reason to get an exception is that the destrcutor is called twice because of wrong code.

Posted 23-Aug-11 2:01am

Philippe Mori

Stefan_Lang · Answer 3 · 2011-08-23T02:14:00

The problem is not in your class definition, it is in the code that uses it.

Although... since you inherit CSnp from CObject you should make your destructor virtual, unless you are absolutely sure that no class will ever inherit from CSnp! (but that is most likely not the cause of your problem)

An exception during delete may be caused by

1. the implementation of CSnp::~CSnp() (e. g. by calling virtual functions or accessing other data that's already destroyed)

2. calling delete[] when delete was called for or vice versa

3. repeated call of the destructor, e. g. because somewhere it's called directly (this might happen in case 2 above, or when your object(s) is stored in some container that takes special care of destruction and you do so as well)

4. plenty of other causes that are pretty hard to determine without using the debugger (in other words, if it's none of the above, use the debugger!)