Mail Archives: djgpp/1997/04/23/15:54:52
In article <335d250f DOT 178260 AT news DOT ucalgary DOT ca>, dunkelzan AT geocities DOT com (Paul Szuch) writes:
|>I am gettings a sigsev at Malloc +194. Can anyone give a suggestion as
|>to how I am causing this?
|>
Usually by corrupting one of the blocks you have malloced (writing off
the end of it, or writing before the beginning) or, less likely, by corrupting
malloc's internal tables. You have a pointer problem or some problem
with the size of things (e.g. you allocate 16 bytes but use 17)
A debugging malloc library, which validates all of malloc's tables
and the entire linked list of malloc'ed blocks at each call, would help
you track this down a bit.
------------------------------------------------------------------------------
Kevin Ashley K DOT Ashley AT Ulcc DOT ac DOT uk
Development Manager http://www.ulcc.ac.uk/staff/Kevin+Ashley
University of London Computer Centre. ...ukc!ncdlab!K.Ashley
This is not a signature
- Raw text -