From: Randolph Chung <randolph@tausq.org>
To: parisc-linux@parisc-linux.org
Subject: [parisc-linux] segfaults with new binutils
Date: Sat, 10 Mar 2001 09:39:42 -0700 [thread overview]
Message-ID: <20010310093942.O18113@tausq.org> (raw)
I'm using binutils from
ftp://puffin.external.hp.com/pub/parisc/binaries/new-debs/debian/
with the corresponding libc6/libc6-dev in that directory, and using the
new gcc-2.97 packages.
Running any of the binaries in the binutils deb gives an immediate
segfault. This includes things like as, ld, etc... obviously this makes
it rather difficult to compile anything.. :-(
I've tried this with both 32-bit and 64-bit kernels built from
yesterday's cvs. Also, at taggart's advice, tried an older 32-bit kernel
built from Feb21 CVS (that was the date of the kernel he was using.)
This is on a C3k.
strace gives:
[...]
open("/lib/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\2\1\3\0\0\0\0\0\0\0\0\0\3\0\17\0\0\0\1\0\2\205"..., 1024) = 1
024
newfstat(3, {st_mode=S_IFREG|0755, st_size=1281732, ...}) = 0
close(3) = 0
munmap(0x4001d000, 7026) = 0
getpid() = 9829
--- SIGSEGV (Segmentation fault) ---
+++ killed by SIGSEGV +++
I rebuilt binutils using an earlier nfsroot (so, older binutils/glibc/gcc
combo) and the resulting binutils binaries work ok with the new
os/kernel/libc/gcc combo.
ideas, hints, fixes? :)
randolph
--
@..@ http://www.TauSq.org/
(----)
( >__< )
^^ ~~ ^^
next reply other threads:[~2001-03-10 16:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-10 16:39 Randolph Chung [this message]
2001-03-10 17:21 ` [parisc-linux] segfaults with new binutils Randolph Chung
2001-03-11 2:55 ` Alan Modra
2001-03-11 3:31 ` Alan Modra
2001-03-11 12:50 ` Matthew Wilcox
2001-03-11 16:49 ` Randolph Chung
2001-03-11 23:44 ` Alan Modra
2001-03-11 16:55 ` Randolph Chung
2001-03-11 23:41 ` Alan Modra
2001-03-12 4:31 ` Jes Sorensen
2001-03-12 4:55 ` Alan Modra
2001-03-12 5:04 ` Randolph Chung
[not found] <Pine.LNX.4.21.0103141045320.27636-100000@front.linuxcare.com.au>
2001-03-14 0:22 ` Alan Modra
2001-03-14 4:24 ` Alan Modra
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=20010310093942.O18113@tausq.org \
--to=randolph@tausq.org \
--cc=parisc-linux@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.