linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Rumler <Steffen.Rumler@icn.siemens.de>
To: linuxppc <linuxppc-embedded@lists.linuxppc.org>
Subject: Accessing the user stack inside system call service routine
Date: Thu, 13 Jun 2002 09:43:27 +0200	[thread overview]
Message-ID: <3D084D1F.95AFFCBB@icn.siemens.de> (raw)


Hello,

I want to access/record the user stack within the system call
service routine sys_sigsuspend() (arch/ppc/signal.c),
in order to debug hanging threads.

The user register context is passed to sys_sigsuspend() via
the 'struct pt_regs *regs' argument.

In this way I can obtain the stack pointer r1
(via regs->gpr[1]) and catch the PPC EABI stack frames.

But I see all zeros behind 'regs->gpr[1]' instead of proper
stack frames. What is wrong ?

How can I access the user stack within a
system call service routine (sys_XXX) ?

Thank you for help,


Steffen

--


--------------------------------------------------------------

Steffen Rumler
ICN ON PNE SB 4
Siemens AG
Hofmannstr. 51                 Email: Steffen.Rumler@icn.siemens.de
D-81359 Munich                 Phone: +49 89 722-44061
Germany                        Fax  : +49 89 722-36703

--------------------------------------------------------------

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2002-06-13  7:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13  7:43 Steffen Rumler [this message]
2002-06-13 11:10 ` Accessing the user stack inside system call service routine Neil Horman
2002-06-13 14:20   ` Steffen Rumler
2002-06-13 15:11     ` Neil Horman
2002-06-13 21:46     ` Paul Mackerras
2002-06-13 22:28       ` Frank Rowand
2002-06-19 11:40       ` Steffen Rumler

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=3D084D1F.95AFFCBB@icn.siemens.de \
    --to=steffen.rumler@icn.siemens.de \
    --cc=linuxppc-embedded@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).