From: Fuxin Zhang <fxzhang@ict.ac.cn>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Srinivas Kommu <kommu@hotmail.com>, linux-mips@linux-mips.org
Subject: Re: how to get a process backtrace from kernel gdb?
Date: Wed, 22 Mar 2006 19:40:38 +0800 [thread overview]
Message-ID: <442137B6.60705@ict.ac.cn> (raw)
In-Reply-To: <20060322113203.GA4544@linux-mips.org>
>
> a) Analyze the code with a simple frame unwinder along the lines of the
> get_wchan implementation. Simple but possibly fragile as compilers
> continue to improve.
> b) Bite the bullet and use the DWARD 2 frame unwind info and code. More
> complicated but will be a solid and correct solution albeit larger so
> not acceptable for small embedded devices.
>
> I fear we may have to do both, 2) as the prefered solution and 1) as the
> fallback solution.
OK, thanks. I will have a look at IA64's implementation and port it if
possible.
>
> Ralf
>
>
>
next prev parent reply other threads:[~2006-03-22 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 0:02 how to get a process backtrace from kernel gdb? Srinivas Kommu
2006-03-22 10:50 ` Ralf Baechle
2006-03-22 11:11 ` Fuxin Zhang
2006-03-22 11:32 ` Ralf Baechle
2006-03-22 11:40 ` Fuxin Zhang [this message]
2006-03-22 12:04 ` Ralf Baechle
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=442137B6.60705@ict.ac.cn \
--to=fxzhang@ict.ac.cn \
--cc=kommu@hotmail.com \
--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