public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: n0ano@indstorage.com
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] unw_init_frame_info() and activation records
Date: Tue, 16 Apr 2002 22:35:37 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590701905463@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590701905462@msgid-missing>

All-

Just a friendly note from the mailing list administrator.  I let this
post go through but this is probably something that should have been
put up on an `ftp' server somewhere with a note about it's existence
sent to the list.  I don't want to put hard size limits on anyone but
we all should use common sense and use `ftp' servers where appropriate.

Tnx.

On Tue, Apr 16, 2002 at 02:55:21PM -0700, Piet/Pete Delaney wrote:
> Hi Keith:
> 
> Our linux lcrash code support for stack frames needs improvement, I'm
> looking around for code to pinch and was wondering about the kdb code.
> 
> The kdb code at least seems to support the NEW_UNWIND code by using 
> unw_init_frame_info().  You code mentions that it should be using activation 
> records and I was wondering what that's all about.
> 
> I've been reading Davie Mosberger chapter on Stack Unwinding and I'll check the
> kernel code for perspectives on the code. I suspect that the gdb unwind code
> and the HP-IPF-unwind library (see attached) are likely an overkill and only
> needed for C++.
> 
> Perhaps you could take a few minutes and provide a few pointers on how
> to save time in adding unwind support. 
> 
> -piet
> 
> 
> 



-- 
Don Dugger
"Censeo Toto nos in Kansa esse decisse." - D. Gale
n0ano@indstorage.com
Ph: 303/652-0870x117


      reply	other threads:[~2002-04-16 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16 21:55 [Linux-ia64] unw_init_frame_info() and activation records Piet/Pete Delaney
2002-04-16 22:35 ` n0ano [this message]

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=marc-linux-ia64-105590701905463@msgid-missing \
    --to=n0ano@indstorage.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