From: Andreas Schwab <schwab@suse.de>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] pthread failure ???
Date: Thu, 13 Jun 2002 08:59:24 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590701905669@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905668@msgid-missing>
Jack Steiner <steiner@sgi.com> writes:
|> We have a pthread'ed application that ran fine on IA64 2.4.17.
|>
|> When we upgraded the kernel to 2.4.18, the application started to
|> fail. The failure occurs in glibc at:
|> chunk_free
|> __libc_free
|> ...
Please define "failure".
|> Has anyone else seen this behavior or have any ideas??
Check your malloc/realloc/free calls, use a malloc debugger (see the
glibc manual for the glibc internal one).
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2002-06-13 8:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 0:56 [Linux-ia64] pthread failure ??? Jack Steiner
2002-06-13 8:59 ` Andreas Schwab [this message]
2002-06-13 15:25 ` David Mosberger
2002-06-13 18:14 ` Jack Steiner
2002-06-13 18:26 ` David Mosberger
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=marc-linux-ia64-105590701905669@msgid-missing \
--to=schwab@suse.de \
--cc=linux-ia64@vger.kernel.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.