From: Keith Owens <kaos@ocs.com.au>
To: linux-kernel@vger.kernel.org
Subject: Announce: ksymoops 2.4.6 is available (reissue)
Date: Fri, 26 Jul 2002 08:41:42 +1000 [thread overview]
Message-ID: <2770.1027636902@ocs3.intra.ocs.com.au> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Content-Type: text/plain; charset=us-ascii
Reissued to add note about binutils problems.
ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops/v2.4
ksymoops-2.4.6.tar.gz Source tarball, includes RPM spec file
ksymoops-2.4.6-1.src.rpm As above, in SRPM format
ksymoops-2.4.6-1.i386.rpm Compiled with 2.96 20000731, glibc 2.2.2
patch-ksymoops-2.4.6.gz Patch from ksymoops 2.4.5 to 2.4.6.
Changelog extract
* m68k call trace does not have trailing ' '. Reported by
Richard Zidlicky.
* MIPS has a hole in the register dump, skip $26 and $27 (k0, k1).
Maciej W. Rozycki.
* Only print decoded registers if they resolve to kernel symbols.
Some people have reported problems building ksymoops, with unresolved
references in libbfd (htab_create, htab_find_slot_with_hash). Try
http://www.cs.helsinki.fi/linux/linux-kernel/2002-13/0196.html first,
if that does not work, contact the binutils maintainers. This is not a
ksymoops problem, ksymoops only uses libbfd. Any unresolved references
from libbfd are a binutils problem.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Exmh version 2.1.1 10/15/1999
iD8DBQE9QH6li4UHNye0ZOoRAkZUAJ0QKS7WBytWlttPqoE0ZdMy9RvN9wCgk4+J
XfAo0yeBJDKa4Q0iDL4ZKn4=
=bUSD
-----END PGP SIGNATURE-----
reply other threads:[~2002-07-25 22:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2770.1027636902@ocs3.intra.ocs.com.au \
--to=kaos@ocs.com.au \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®