l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2012 May 14 20:41

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] C++ problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] C++ problem

Using delete[] for an array allocated with new[] is correct, so I
don't think you've given us enough information to find the bug.

Are you getting any compiler warnings or errors?
Have you tried compiling with -Wall and -Wextra?
Are any of these overwritten variables pointers into the array var?
Could the array size stored at address (var - 4) have been overwritten
by accident by some other code?
Have you tried using valgrind to automatically find an accidental
overwrite earlier in execution?


On Sat, May 12, 2012 at 11:38 PM, Jeff Newmiller
<jdnewmil@dcn.davis.ca.us> wrote:
> It did make it to me, but
> a) I am out of town away from computers, and
> b) without a working example I probably would not look at it very closely
> ---------------------------------------------------------------------------
> Jeff Newmiller                        The     .....       .....  Go Live...
> DCN:<jdnewmil@dcn.davis.ca.us>        Basics: ##.#.       ##.#.  Live Go...
>                                      Live:   OO#.. Dead: OO#..  Playing
> Research Engineer (Solar/Batteries            O.O#.       #.O#.  with
> /Software/Embedded Controllers)               .OO#.       .OO#.  rocks...1k
> ---------------------------------------------------------------------------
> Sent from my phone. Please excuse my brevity.
> Richard Harke <paleopenguin@gmail.com> wrote:
>>My last post seems to have gotten lost so I'll try again.
>>I'm working on a small C++ program. In one of the constructors I
>>create an array with
>>double * var = new double [size]   After use, before exiting the
>>constructor I return the memory with delete [] var  But after return
>>from the delete, several private class variables are written over.
>>I have checked that these variables are correct just before the delete
>>call and are modified right after. Does anyone have any idea what is
>>going on?
>>I'm running debian squeeze for amd64  with gcc 4.4.5 This morning I
>>did an apt-get upgrade to be sure I had any recent fixes.
>>Richard Harke
>>vox-tech mailing list
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech
vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
Appahost Applications
For a significant contribution towards our projector, and a generous donation to allow us to continue meeting at the Davis Library.