From: "Boehm, Hans" <hans_boehm@hp.com>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: FW: [ia64-tools] Gdb error message
Date: Tue, 27 Feb 2001 12:38:00 -0000 [thread overview]
Message-ID: <140D21516EC2D3119EE7009027876644049B5C3E@hplex1.hpl.hp.com> (raw)
Kevin Buettner suggested I repeat this question here.
This is on an Itanium machine running a recent Red Hat installation. Can
anyone interpret the error message:
internal error - unimplemented function unk_lang_create_fundamental_type
called.
or suggest a plausible workaround?
Thanks.
Hans
-----Original Message-----
From: Boehm, Hans [ mailto:hans_boehm@hp.com ]
Sent: Tuesday, February 27, 2001 10:58 AM
To: hboehm@napali.hpl.hp.com
Subject: [ia64-tools] Gdb error message
I'm trying to debug some miscompiled executables generated by gcj. I'm
using gdb 5.0 from an rpm package gdb-5.0-7. The executable is statically
linked, but multithreaded.
I seem to have gotten into a rut where almost anything results in the error
message:
internal error - unimplemented function unk_lang_create_fundamental_type
called.
This is after a few other errors on process startup:
warning: unable to set global thread event mask
rw_common (): write: No such file or directory.
warning: stop_or_attach_thread: generic error
Can anyone interpret this? This seems like unfriendly behavior from gdb,
even if it's being fed garbage. Is there a fixed version of gdb? (I don't
know how correct or incorreect the gcj-generated debug information is. I
recall seeing the process startup errors also with statically linked C code.
The behavior is the same whether I compile with -g or not. It's different
on a stripped executable, but unsurprisingly that doesn't get far either.)
Thanks.
Hans
next reply other threads:[~2001-02-27 12:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-27 12:38 Boehm, Hans [this message]
2001-02-27 18:37 ` Daniel Berlin
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=140D21516EC2D3119EE7009027876644049B5C3E@hplex1.hpl.hp.com \
--to=hans_boehm@hp.com \
--cc=gdb@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