public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cseddon at sequencedesign dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug libc/3455] ptmalloc fails if foreign sbrk and no mmap and size is greater than  trim threshold
Date: Fri, 03 Nov 2006 19:22:00 -0000	[thread overview]
Message-ID: <20061103192236.30664.qmail@sourceware.org> (raw)
In-Reply-To: <20061103173516.3455.cseddon@sequencedesign.com>


------- Additional Comments From cseddon at sequencedesign dot com  2006-11-03 19:22 -------
_I_ did not use sbrk().  A third-party package did.

My test program does, but only to provide a demostration of the problem.

malloc has all sorts of special-casing in it for handling 'foreign sbrk'.  It
appears to be programmed to handle the foreign sbrk(), but fails to do so.

If it is impossible to use sbrk(), then shouldn't it's prototype be removed?

-charlie

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|INVALID                     |


http://sourceware.org/bugzilla/show_bug.cgi?id=3455

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


  parent reply	other threads:[~2006-11-03 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-03 17:35 [Bug libc/3455] New: " cseddon at sequencedesign dot com
2006-11-03 17:44 ` [Bug libc/3455] " drepper at redhat dot com
2006-11-03 19:22 ` cseddon at sequencedesign dot com [this message]
2006-11-03 20:59 ` drepper at redhat dot com
2006-11-04 13:40 ` cseddon at sequencedesign dot com

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=20061103192236.30664.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sources.redhat.com \
    /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).