From: Vladimir Simonov <sv@sw.com.sg>
To: linux-ia64@vger.kernel.org
Subject: [Linux-ia64] show_trace_task portability
Date: Fri, 21 Mar 2003 09:36:23 +0000 [thread overview]
Message-ID: <marc-linux-ia64-105590723705283@msgid-missing> (raw)
[-- Attachment #1: Type: text/plain, Size: 423 bytes --]
Hi!
Trying to port some patches from i386 to ia64 I've found that
show_trace_task is the only portable way to show tasks' call
traces(perhaps because it is called from ./kernel/sched.c:)).
But its ia64 implementation can't work with running task.
Attached patch fixes this issue.
As I understand show_trace and show_stack are platform
dependent or have different sense/args.
Any opinion?
Best regards
Vladimir Simonov
[-- Attachment #2: diff-show_trace_task.ia64 --]
[-- Type: text/plain, Size: 335 bytes --]
--- linux.orig/arch/ia64/kernel/process.c Fri Mar 21 08:32:37 2003
+++ linux/arch/ia64/kernel/process.c Fri Mar 21 08:53:06 2003
@@ -53,10 +53,7 @@
void
show_trace_task (struct task_struct *task)
{
- struct unw_frame_info info;
-
- unw_init_from_blocked_task(&info, task);
- do_show_stack(&info, 0);
+ show_stack(task);
}
void
next reply other threads:[~2003-03-21 9:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 9:36 Vladimir Simonov [this message]
2003-03-21 19:45 ` [Linux-ia64] show_trace_task portability David Mosberger
2003-04-16 16:09 ` Bjorn Helgaas
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-105590723705283@msgid-missing \
--to=sv@sw.com.sg \
--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