From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [RFC] Enhanced show_stack output to add backing store regs
Date: Fri, 11 Mar 2005 20:59:15 +0000 [thread overview]
Message-ID: <16946.1699.493614.729130@napali.hpl.hp.com> (raw)
In-Reply-To: <1110566404.498.79.camel@localhost.localdomain>
>>>>> On Fri, 11 Mar 2005 20:25:26 +0000, Matthew Wilcox <matthew@wil.cx> said:
Matthew> I know your patch leaaves this unchanged, but I don't think it's helpful
Matthew> to show the 'show_stack' and 'show_regs' frames. Can we get rid of them,
Matthew> or is there a reason they're useful?
There were useful in the early days, when I didn't trust the unwinder... ;-)
I agree that we should drop them. Just unwind to the interruption-frame
(pt_regs), then start printing the frames.
That'll also be more in line with the other arches.
--david
next prev parent reply other threads:[~2005-03-11 20:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-11 18:40 [RFC] Enhanced show_stack output to add backing store regs Bob Montgomery
2005-03-11 19:12 ` Chen, Kenneth W
2005-03-11 20:25 ` Matthew Wilcox
2005-03-11 20:59 ` David Mosberger [this message]
2005-03-11 21:00 ` Luck, Tony
2005-03-11 21:19 ` Bob Montgomery
2005-03-11 21:23 ` David Mosberger
2005-03-14 18:51 ` Alex Tsariounov
2005-03-14 19:04 ` Luck, Tony
2005-03-14 19:19 ` Alex Tsariounov
2005-03-14 23:06 ` Keith Owens
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=16946.1699.493614.729130@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=linux-ia64@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