From: Hollis Blanchard <hollis@amulet.co.jp>
To: Nathan Ingersoll <ningerso@d.umn.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Malloc bug?
Date: Wed, 19 Jul 2000 11:51:30 +0900 [thread overview]
Message-ID: <397517B2.8F22EDEA@amulet.co.jp> (raw)
In-Reply-To: Pine.SO4.4.02.10007181457570.7001-100000@ub.d.umn.edu
Nathan Ingersoll wrote:
>
> I've been working on a GTK program for a while now, and I've been
> experiencing segfaults within malloc.
In my experience this is almost always caused by overwriting array
bounds somewhere before that. (Learning how malloc works helps you
understand why.) Go check all your memory accesses. Electric Fence might
help.
-Hollis
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-07-19 2:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-18 20:40 Malloc bug? Nathan Ingersoll
2000-07-18 20:54 ` Paul Schinder
2000-07-18 21:30 ` Nathan Ingersoll
2000-07-18 21:37 ` David Edelsohn
2000-07-19 2:01 ` Sean Chitwood
2000-07-18 22:37 ` David A. Gatwood
2000-07-18 22:03 ` David A. Gatwood
2000-07-19 16:30 ` William Blew
2000-07-19 17:19 ` Paul Schinder
2000-07-19 23:06 ` David A. Gatwood
2000-07-19 18:28 ` Nathan Ingersoll
2000-07-19 23:03 ` David A. Gatwood
2000-07-19 2:51 ` Hollis Blanchard [this message]
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=397517B2.8F22EDEA@amulet.co.jp \
--to=hollis@amulet.co.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=ningerso@d.umn.edu \
/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 NNTP newsgroup(s).