All of lore.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: "linuxppc-embedded@lists.linuxppc.org"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: brk() problem in glibc 2.3.2 on TQM860
Date: Wed, 30 Jun 2004 00:01:07 -0400	[thread overview]
Message-ID: <40E23B03.5030701@opersys.com> (raw)
In-Reply-To: <40DFB360.3090801@opersys.com>


... Pilot error ...

Karim Yaghmour wrote:
> I've been having problems with brk() calls (like ones made by malloc()
> to the
> kernel) when using glibc 2.3.2 on a TQM860 (16MB RAM, 8MB of flash.)
> Take the
> following snippet of code for example:
>     for (i = 1, val = 10; i < 10; val = val * 10, i++) {
>         printf("Allocating %lu \n", val);
>         x = (void*) malloc(val);
>         memset(x, '\0', val);
>     }

It actually freezes in the memset() and the problem is the memset.S file in
glibc-2.3.2/sysdeps/powerpc/powerpc32/ which needs to be removed. I knew
this problem existed in older versions of glibc, but I had assumed that it
had been fixed in the newer versions ... I assumed wrong.

When the file is removed everything works fine.

Karim
--
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2004-06-30  4:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28  5:57 brk() problem in glibc 2.3.2 on TQM860 Karim Yaghmour
2004-06-30  4:01 ` Karim Yaghmour [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=40E23B03.5030701@opersys.com \
    --to=karim@opersys.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.