From: Ulrich Drepper <drepper@cygnus.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: libc-hacker@sourceware.cygnus.com
Subject: Re: interesting change
Date: Fri, 30 Jul 1999 23:18:00 -0000 [thread overview]
Message-ID: <m31zdp2vne.fsf@localhost.localnet> (raw)
In-Reply-To: <19990731080219.A6381@Wotan.suse.de>
Thorsten Kukuk <kukuk@suse.de> writes:
> There are some more problems with the your __libc_pagesize optimization.
> The list of commercial applications crashing with this patch enlarges
> every week.
> It seems all of this application uses it's own malloc functions.
Well, if they are using their own malloc, how can this be a problem?
The initialization happens at the right time. It can only be that
these application do something forbidden.
--
---------------. drepper at gnu.org ,-. 1325 Chesapeake Terrace
Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1999-07-30 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-30 22:20 Ulrich Drepper
1999-07-30 23:04 ` Thorsten Kukuk
1999-07-30 23:18 ` Ulrich Drepper [this message]
1999-07-30 23:52 ` Thorsten Kukuk
1999-07-31 0:00 ` Ulrich Drepper
1999-07-31 20:42 ` Geoff Keating
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=m31zdp2vne.fsf@localhost.localnet \
--to=drepper@cygnus.com \
--cc=kukuk@suse.de \
--cc=libc-hacker@sourceware.cygnus.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).