From: "gmoreira at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/22671] MIPSEL error Unknown register: a4
Date: Thu, 26 Apr 2018 07:50:00 -0000 [thread overview]
Message-ID: <bug-22671-6586-OLt89LqHgS@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-22671-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=22671
Gustavo Moreira <gmoreira at gmail dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gmoreira at gmail dot com
--- Comment #7 from Gustavo Moreira <gmoreira at gmail dot com> ---
Created attachment 10988
--> https://sourceware.org/bugzilla/attachment.cgi?id=10988&action=edit
MIPS o32 ABI patch
This is based on arch/mips/include/ptrace.h and ARM registers.stp.
However, it doesn't seem to be working correctly, the values extracted from the
user stack, for some reason, aren't the correct ones.
I would appreciate if you can review the patch and help me out.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2018-04-26 7:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-04 6:42 [Bug runtime/22671] New: " mysecondaccountabc at gmail dot com
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 [this message]
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-OLt89LqHgS@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).