Quoting Ron Cole <rcole@EZY.NET>: > They are all crashes in memory allocation calls which makes no sense > to me, if the memory allocation code was buggy, the whole system would be > unstable. Here's a sample core. I've seen this problem several times before myself. Normally the error is due to corruption of the malloc heap which is causing the failure later on when more memory is requested. In short, you are doing something funky (over- or under-writing, double freeing) with malloced memory which is causing this problem. You might try using ValGrind (http://developer.kde.org/~sewardj/) to catch problems like these. -Brian -- +---------------------------------------------------------------+ | FAQ: http://qsilver.queensu.ca/~fletchra/Circle/list-faq.html | | Archives: http://post.queensu.ca/listserv/wwwarch/circle.html | | Newbie List: http://groups.yahoo.com/group/circle-newbies/ | +---------------------------------------------------------------+
This archive was generated by hypermail 2b30 : 06/25/03 PDT