X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-bounces using -f
Date:	Sun, 14 Apr 2002 21:31:45 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<6551-Sun14Apr2002213144+0300-eliz@is.elta.co.il>
X-Mailer:	emacs 21.2.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to:	<muejbu0q7l4e2s57sdkokclabnh7b1i2es@4ax.com> (message from Bernd
	Becker on Sun, 14 Apr 2002 19:37:28 +0200)
Subject:	Re: GPP 3.04: unknown (to me) error in crash log
References:	<n33gbug7s08o8lh8chokjrv4rtjv7849rq AT 4ax DOT com> <7680-Sat13Apr2002211933+0300-eliz AT is DOT elta DOT co DOT il> <cvugbuohjq6c4qqn46fpir7a8v6ikss21s AT 4ax DOT com> <2927-Sun14Apr2002065236+0300-eliz AT is DOT elta DOT co DOT il> <muejbu0q7l4e2s57sdkokclabnh7b1i2es AT 4ax DOT com>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: Bernd Becker <munin AT munin DOT inka DOT de>
> Newsgroups: comp.os.msdos.djgpp
> Date: Sun, 14 Apr 2002 19:37:28 +0200
> >
> >    I searched in the 'info' directory and with 'Google' on the web for
> >    some information about the '___cxa_bad_typeid' error but neither was
> >    successful. Does anybody here know what this error message means ??
> >
> >I understood ``this error message'' as a reference to the crashe
> >message printed when the program segfaults.  What other message was
> >in your post?
> ??Huh??
> Sorry, but no matter how I read that question, I ask what
> ___cxa_bad_typeid means and nothing else. 

You used the phrase "error message", but the line that mentions
'___cxa_bad_typeid':

  0x0006f8ce ___cxa_bad_typeid+1394

doesn't look as an error message.  That's why I thought you were
talking about the crash message, which does look like error message:

  General Protection Fault at eip=000594a5

Anyway, since we are both not native English speakers, it should be no
surprise that this misunderstanding happened.  There's no need to be
so upset because of that.

> >Then I don't understand your question at all.  Your program crashed
> >because it somehow corrupted the malloc memory chain.  Given that, why
> >is it important to know what is '___cxa_bad_typeid'?
> Because it never appeared before, it seems to indicate part of the
> problem why 'free' crashes, and because I don't know what it means,

When the chain of memory managed by malloc is corrupted, _any_
function that calls malloc or free can crash.  So there's nothing
special about '___cxa_bad_typeid' in your case; that function has
nothing to do with the reasons your program crashes.

> Are
> these enough reasons for you, or can we just say that you don't know
> what '___cxa_bad_typeid' means and were pointing out the obvious as it
> was something you did know ???

We can say something else--that I was trying to help you understand
the _real_ reasons for your crash, and in response got the kind of
nasty attitude that will make me think twice before trying to help
you next time.

- Raw text -