segfaults are caused much easier than that. The most common causes are
referencing a bit of memory that has already been freed. Another cause is
freeing a bit of memory which has already been freed (this is very bad,
and can cause errors in weird locations).
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Tue, 23 Nov 1999, Bas van Gils wrote:
> Good morning ...
>
> This is waaaayyyy out of my league, but I want to give it a shot anyway.
> Segv refers to a segmentationfault (at least, that's what I assume ;)...)
> so we have a memory-problem. Aparantly there is an object in the memory
> (with it's on segment) and one is trying to reference it. This is where it
> goes wrong... Possible reason: corrupt virtual-page-table is corrupt.
>
> I know this doesnt actually *solve* the problem but it might give someone
> an idea ... ?
>
> Bas
>
> --
> Bas van Gils ([EMAIL PROTECTED]) http://stuwww.kub.nl/people/b.vangils
> tel# +31-6-24614919 (also SMS) fax# +49-89-66617-61693
> System Administrator of StuWWW at http://stuwww.kub.nl/
> Student of Information Management and Technology at Tilburg University
>
> The author of this E-mail requests that you regard this as a private message.
> Please do NOT distribute it! Thank you very much in advance...
>
