From: Christoph Rohland <cr@sap.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] ld failure
Date: Tue, 09 May 2000 17:56:40 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590678205076@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590678205047@msgid-missing>
Uros Prestor <uros@turbolinux.com> writes:
> Christoph Rohland wrote:
>
> > This problem is solved with the new gnupro toolkit included on TL
> > 0505. (Of course I get now an íllegal instruction'when running the
> > executable due to the missing brl emulation in the kernel.)
>
> Try the new kernel RPM available on our update site:
>
> ftp://ftp.turbolinux.com/pub/ia64/0505/updates/RPMS/ia64/kernel-2.3.99-19.ia64.rpm
This now does not generate an ill instruction, but a seg fault in:
$ gdb dw
GNU gdb 20000204
Copyright 2000 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "ia64-unknown-linux"...
(gdb) r
Starting program: /bas/46B/gen/opt/linuxia64/dw
Program received signal SIGSEGV, Segmentation fault.
0x4000000001a7e880 in __do_global_ctors_aux ()
(gdb) bt
#0 0x4000000001a7e880 in __do_global_ctors_aux ()
#1 0x4000000000004a20 in _init ()
(gdb)
Greetings
Christoph
next prev parent reply other threads:[~2000-05-09 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-26 14:09 [Linux-ia64] ld failure Christoph Rohland
2000-04-26 18:58 ` Jim Wilson
2000-04-26 20:58 ` Saxena, Sunil
2000-04-27 17:39 ` Christoph Rohland
2000-05-02 22:32 ` Jim Wilson
2000-05-03 7:33 ` Christoph Rohland
2000-05-09 16:52 ` Christoph Rohland
2000-05-09 17:36 ` Uros Prestor
2000-05-09 17:56 ` Christoph Rohland [this message]
2000-05-24 9:52 ` Christoph Rohland
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-105590678205076@msgid-missing \
--to=cr@sap.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox