Date: Wed, 12 Jan 2000 09:05:25 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Chad Rabbitt <chad AT rabbitt DOT com>
cc: djgpp AT delorie DOT com
Subject: Re: sigsegv on delete []
In-Reply-To: <85go87$hht@chronicle.concentric.net>
Message-ID: <Pine.SUN.3.91.1000112090254.28074Q-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 11 Jan 2000, Chad Rabbitt wrote:

>    0x.....  _free+somenumber
>    0x.....  ___builtin_vec_delete+somenumber, line 0 of new2.cc
>    0x.....  _main+somenumber, line xx of main.cpp
>    etc...
> 
> what is causing sigsegv's on a delete [] statement?

Usually this happens when you either write past the end of allocated 
buffers, or try to free them more than once.

Try using YAMD to find this bug.

If you want more intelligent help, post the entire crash message, 
complete with registers' dump and call frame traceback, after running 
SYMIFY on it.