From: David Edelsohn <dje@watson.ibm.com>
To: Nathan Ingersoll <ningerso@d.umn.edu>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Malloc bug?
Date: Tue, 18 Jul 2000 17:37:09 -0400 [thread overview]
Message-ID: <200007182137.RAA28182@mal-ach.watson.ibm.com> (raw)
In-Reply-To: Message from Nathan Ingersoll <ningerso@d.umn.edu> of "Tue, 18 Jul 2000 16:30:27 CDT." <Pine.SO4.4.02.10007181627250.11229-100000@ub.d.umn.edu>
>>>>> Nathan Ingersoll writes:
Nathan> On Tue, 18 Jul 2000, Paul Schinder wrote:
>> At 3:40 PM -0500 7/18/00, Nathan Ingersoll wrote:
>> >I've been working on a GTK program for a while now, and I've been
>> >experiencing segfaults within malloc. I was under the impression that
>> >malloc should always return successfully (at least that's what the man
>> >page says).
Nathan> Right, but it's not returning at all. It's segfaulting inside the malloc
Nathan> function before it returns anything.
Sounds more like something is overwriting one of malloc's internal
data areas or possibly hitting some weird ulimit symptom.
David
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-07-18 21:37 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 [this message]
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
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=200007182137.RAA28182@mal-ach.watson.ibm.com \
--to=dje@watson.ibm.com \
--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).