From: "mysecondaccountabc at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22671] New: MIPSEL error Unknown register: a4
Date: Thu, 04 Jan 2018 06:42:00 -0000 [thread overview]
Message-ID: <bug-22671-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=22671
Bug ID: 22671
Summary: MIPSEL error Unknown register: a4
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: runtime
Assignee: systemtap at sourceware dot org
Reporter: mysecondaccountabc at gmail dot com
Target Milestone: ---
Created attachment 10711
--> https://sourceware.org/bugzilla/attachment.cgi?id=10711&action=edit
kernel config
Having this error on mipsel emulation:
...
stapio:stp_main_loop:861 systemtap_module_init() returned 0
ERROR: Unknown register: a4
stapio:stp_main_loop:852 got STP_REQUEST_EXIT
WARNING: Number of errors: 1, skipped probes: 0
stapio:stp_main_loop:841 got STP_EXIT
stapio:cleanup_and_exit:526 detach=0
...
# stap --version
Systemtap translator/driver (version 3.2/0.168, non-git sources)
Copyright (C) 2005-2017 Red Hat, Inc. and others
This is free software; see the source for copying conditions.
tested kernel versions: 2.6.18 ... 4.11
enabled features: AVAHI LIBSQLITE3 NLS NSS
# uname -a
Linux arex-11f9b261f2 4.9.0-4-4kc-malta #1 Debian 4.9.65-3 (2017-12-03) mips
GNU/Linux
The Rootfs is a Debian Stretch.
It seems to be an ABI (O32/N32) issue, but not sure why it's happening. I've
locally compiled SystemTap from Systemtap 3.2 release
(https://sourceware.org/systemtap/ftp/releases/systemtap-3.2.tar.gz)
Any clue?
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2018-01-04 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 6:42 mysecondaccountabc at gmail dot com [this message]
2018-01-05 14:25 ` [Bug runtime/22671] " dsmith at redhat dot com
2018-01-08 0:43 ` mysecondaccountabc at gmail dot com
2018-01-15 18:31 ` dsmith at redhat dot com
2018-01-26 21:26 ` dsmith at redhat dot com
2018-02-26 3:48 ` gmoreira at gmail dot com
2018-02-26 22:08 ` dsmith at redhat dot com
2018-04-26 7:50 ` gmoreira at gmail dot com
2018-04-26 20:59 ` fche at redhat dot com
2023-12-06 15:31 ` wcohen at redhat dot com
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=bug-22671-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).