public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "drow at sources dot redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/3775] kernel's zlib code upgrade triggers glibc>=2.4 misbehaviour
Date: Sun, 24 Dec 2006 04:47:00 -0000 [thread overview]
Message-ID: <20061224044703.15599.qmail@sourceware.org> (raw)
In-Reply-To: <20061220212109.3775.ya-cbou@yandex.ru>
------- Additional Comments From drow at sources dot redhat dot com 2006-12-24 04:47 -------
I think it is entirely implausible that glibc could be at fault. In general
there is very little randomness in application startup; if something works some
of the time and crashes other times, the kernel will be to blame. If you have
more specific information about what's wrong, feel free to reopen when you have
a better idea of what is failing. Dynamic linking on ARM does not even require
cache flushing in userspace.
A good idea might be to find the faulting instruction.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|ASSIGNED |RESOLVED
Resolution| |INVALID
http://sourceware.org/bugzilla/show_bug.cgi?id=3775
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
prev parent reply other threads:[~2006-12-24 4:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 21:21 [Bug ports/3775] New: " ya-cbou at yandex dot ru
2006-12-20 21:22 ` [Bug ports/3775] " ya-cbou at yandex dot ru
2006-12-20 21:37 ` ya-cbou at yandex dot ru
2006-12-23 1:12 ` ya-cbou at yandex dot ru
2006-12-24 4:47 ` drow at sources dot redhat dot com [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=20061224044703.15599.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).