From: Ulrich Drepper <drepper@ipd.info.uni-karlsruhe.de>
To: hjl@lucon.org (H.J. Lu)
Cc: libc-linux@gnu.ai.mit.edu (GNU C Library), egcs@cygnus.com
Subject: Re: egcs 971207 breaks glibc 2
Date: Mon, 08 Dec 1997 16:38:00 -0000 [thread overview]
Message-ID: <x7vhwz74h1.fsf@myware.rz.uni-karlsruhe.de> (raw)
In-Reply-To: <m0xfD1R-0004ecC@ocean.lucon.org>
hjl@lucon.org (H.J. Lu) writes:
> egcs 971207 miscompiled the dynamic linker in glibc 2.1 on linux/x86.
> I cannot duplicate it in a small test case.
Same here. The worst thing is that gdb is after the kernel change not
anymore able to debug the dynamic linker. HJ's patch solves the
problem with the initial message not being displayed anymore but
setting a breakpoint in the dynamic linker (or even getting a
reasonable backtrace) is not possible.
-- Uli
---------------. drepper at gnu.org ,-. Rubensstrasse 5
Ulrich Drepper \ ,-------------------' \ 76149 Karlsruhe/Germany
Cygnus Solutions `--' drepper at cygnus.com `------------------------
next prev parent reply other threads:[~1997-12-08 16:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x7hg8kbigs.fsf@myware.rz.uni-karlsruhe.de>
1997-12-08 15:55 ` H.J. Lu
1997-12-08 16:38 ` Ulrich Drepper [this message]
1997-12-10 1:58 ` Andreas Schwab
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=x7vhwz74h1.fsf@myware.rz.uni-karlsruhe.de \
--to=drepper@ipd.info.uni-karlsruhe.de \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=libc-linux@gnu.ai.mit.edu \
/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).