Article View: gnu.gcc.help
Article #41595Re: Segmentation fault from a call to malloc()
From: Patrick Vestjens
Date: Thu, 14 Mar 1996 00:00
Date: Thu, 14 Mar 1996 00:00
15 lines
1040 bytes
1040 bytes
Kevin Stanton (kevins@ee.pdx.edu) wrote: : I'm running g++ version 2.6.3. : My custom motif application generates a SEG FAULT on a call to : malloc(...). I know there is plenty of memory (and it should return null : anyway it that were the problem anyway, right?). : How can a call to MALLOC seg fault? Some table or something must be : really messed up? You probably overwrite malloc's data structure somewhere else in your program. That can cause malloc to follow invalid pointers causing a segmentation fault. Hard to solve, good luck ... Patrick.
Technical Details
Message-ID:
<1996Mar14.114817.3225@ms.philips.nl>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<4i7jd0$40g@flotsam.ee.pdx.edu>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11318c,e9f0bbedcf508bc8 X-Google-Attributes: gid11318c,public From: Pvestjen@ms.philips.nl (Patrick Vestjens) Subject: Re: Segmentation fault from a call to malloc() Date: 1996/03/14 Message-ID: <1996Mar14.114817.3225@ms.philips.nl> X-Deja-AN: 142648971 sender: news@ms.philips.nl references: <4i7jd0$40g@flotsam.ee.pdx.edu> organization: Philips Medical Systems, Best newsgroups: gnu.gcc.help