From: Alan Stange <stange@rentec.com>
To: help-gcc@gnu.org
Subject: Re: Segmentation fault on malloc call
Date: Thu, 30 Sep 1999 06:12:00 -0000 [thread overview]
Message-ID: <37F3604C.E0971AF7@rentec.com> (raw)
In-Reply-To: <37F35D74.5FCA96B5@Unforgettable.com>
Hi,
The times that I've seen this usually involve stomping on the heap
itself. For example, allocating 16 bytes, but then using 32, etc.
Using purify, you'll find this right away.
Also, try "man watchmalloc" to help chasing down the problem.
--
Alan L. Stange Renaissance Technologies Corp. stange@rentec.com
WARNING: multiple messages have this Message-ID
From: Alan Stange <stange@rentec.com>
To: help-gcc@gnu.org
Subject: Re: Segmentation fault on malloc call
Date: Thu, 30 Sep 1999 23:56:00 -0000 [thread overview]
Message-ID: <37F3604C.E0971AF7@rentec.com> (raw)
Message-ID: <19990930235600.DLcLRqTTOdRPwXt33aqH6L0RXtOOGoSZ4HAmjhWszf8@z> (raw)
In-Reply-To: <37F35D74.5FCA96B5@Unforgettable.com>
Hi,
The times that I've seen this usually involve stomping on the heap
itself. For example, allocating 16 bytes, but then using 32, etc.
Using purify, you'll find this right away.
Also, try "man watchmalloc" to help chasing down the problem.
--
Alan L. Stange Renaissance Technologies Corp. stange@rentec.com
WARNING: multiple messages have this Message-ID
From: Alan Stange <stange@rentec.com>
To: help-gcc@gnu.org
Subject: Re: Segmentation fault on malloc call
Date: Fri, 01 Oct 1999 00:00:00 -0000 [thread overview]
Message-ID: <37F3604C.E0971AF7@rentec.com> (raw)
Message-ID: <19991001000000.tj3MVqT6we-Z5ANrHhhHXBRMXXMsTMg_mkYIMCyoWjo@z> (raw)
In-Reply-To: <37F35D74.5FCA96B5@Unforgettable.com>
Hi,
The times that I've seen this usually involve stomping on the heap
itself. For example, allocating 16 bytes, but then using 32, etc.
Using purify, you'll find this right away.
Also, try "man watchmalloc" to help chasing down the problem.
--
Alan L. Stange Renaissance Technologies Corp. stange@rentec.com
next prev parent reply other threads:[~1999-09-30 6:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-29 13:48 Nawin Somyat
1999-09-30 1:26 ` Casper H.S. Dik - Network Security Engineer
1999-09-30 23:56 ` Casper H.S. Dik - Network Security Engineer
1999-10-01 0:00 ` Casper H.S. Dik - Network Security Engineer
1999-09-30 6:03 ` Kenneth C Stahl
1999-09-30 6:12 ` Alan Stange [this message]
1999-09-30 23:56 ` Alan Stange
1999-10-01 0:00 ` Alan Stange
1999-09-30 23:56 ` Kenneth C Stahl
1999-10-01 0:00 ` Kenneth C Stahl
1999-09-30 23:56 ` Nawin Somyat
1999-10-01 0:00 ` Nawin Somyat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=37F3604C.E0971AF7@rentec.com \
--to=stange@rentec.com \
--cc=help-gcc@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).