From: Randolph Chung <randolph@tausq.org>
To: "Carlos O'Donell Jr." <carlos@megatonmonkey.net>,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Glibc 2.2.4-2 Woes...
Date: Sat, 6 Oct 2001 21:47:06 -0700 [thread overview]
Message-ID: <20011006214706.D3218@tausq.org> (raw)
In-Reply-To: <20011006135558.B8206@megatonmonkey.net>
> The assertion fails.
> The address in r21/r25 is 0x15b78, which is clearly not a valid
> address, and thus dl's printf barfs.
I got the new gcc to build (3.0.2 cvs 20010922) and tried glibc again... it dies
similarly while trying to run ld.so ...
Program received signal SIGSEGV, Segmentation fault.
_dl_debug_vdprintf (fd=0, tag_p=0,
fmt=0x17cdc <Address 0x17cdc out of bounds>, arg=0xbff005d8)
at dl-misc.c:101
101 while (*fmt != '\0')
(gdb) bt
#0 _dl_debug_vdprintf (fd=0, tag_p=0,
fmt=0x17cdc <Address 0x17cdc out of bounds>, arg=0xbff005d8)
at dl-misc.c:101
#1 0x4100eb68 in _dl_dprintf (fd=2,
fmt=0x17cdc <Address 0x17cdc out of bounds>) at dl-misc.c:279
#2 0x41012b6c in __assert_fail (
assertion=0x15bac <Address 0x15bac out of bounds>, file=0x0, line=62,
function=0xbff005d8 "") at dl-minimal.c:190
#3 0x410031d4 in _dl_start (arg=0xbff00224) at rtld.c:62
#4 0x41002af8 in _dl_start_user () at rtld.c:143
I'll try to debug it some more tomorrow.
BenC (debian's glibc maintainer) also claims that the hppa patch in
glibc breaks linuxthreads (runtime) on other architectures. Does anyone
know anything about this?
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next prev parent reply other threads:[~2001-10-07 4:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-06 17:55 [parisc-linux] Glibc 2.2.4-2 Woes Carlos O'Donell Jr.
2001-10-07 4:47 ` Randolph Chung [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-08 8:26 Jurij Smakov
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=20011006214706.D3218@tausq.org \
--to=randolph@tausq.org \
--cc=carlos@megatonmonkey.net \
--cc=parisc-linux@lists.parisc-linux.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.