This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: seg fault using octave with RH 6.0
- To: keitt at nceas dot ucsb dot edu
- Subject: Re: seg fault using octave with RH 6.0
- From: "Martin v. Loewis" <martin at mira dot isdn dot cs dot tu-berlin dot de>
- Date: Wed, 12 May 1999 21:32:42 +0200
- CC: help-octave at bevo dot che dot wisc dot edu, egcs at egcs dot cygnus dot com
- References: <3739CEF8.B5215723@nceas.ucsb.edu>
> Anyone know what is going on with the back trace below?
That's easy: The memory management is messed up (or you are in the
process of messing it up right now). That means: Either you are
deleting an object that has already been deleted, or some earlier
delete made that error, or somebody was overwriting memory through a
bogus pointer.
You might be able to track this down via malloc debugging, please read
the libc info on mcheck(3) and mtrace(3).
Hope this helps,
Martin
P.S. I know nothing about Octave or its loadable modules.