From: minyard@acm.org
To: linux-mips@linux-mips.org, ralf@linux-mips.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] mips: fix various issues around backtrace
Date: Thu, 10 Aug 2017 13:27:36 -0500 [thread overview]
Message-ID: <1502389660-8969-1-git-send-email-minyard@acm.org> (raw)
These are patches for problems I ran into while handling backtrace
issues, both inside Linux and when processing backtraces with gdb
in a kernel dump.
-corey
next reply other threads:[~2017-08-10 18:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-10 18:27 minyard [this message]
2017-08-10 18:27 ` [PATCH 1/4] mips: Fix issues in backtraces minyard
2017-08-10 18:27 ` [PATCH 2/4] mips: Make SAVE_SOME more standard minyard
2017-08-10 18:27 ` [PATCH 3/4] mips: Add DWARF unwinding to assembly minyard
2017-08-10 18:27 ` [PATCH 4/4] mips: Save all registers when saving the frame minyard
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=1502389660-8969-1-git-send-email-minyard@acm.org \
--to=minyard@acm.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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
Powered by JetHome