From: Steffen Rumler <Steffen.Rumler@icn.siemens.de>
To: Paul Mackerras <paulus@samba.org>
Cc: Neil Horman <nhorman@lvl7.com>,
linuxppc <linuxppc-embedded@lists.linuxppc.org>,
Frank Rowand <frank_rowand@mvista.com>
Subject: Re: Accessing the user stack inside system call service routine
Date: Wed, 19 Jun 2002 13:40:50 +0200 [thread overview]
Message-ID: <3D106DC2.B50D7100@icn.siemens.de> (raw)
In-Reply-To: 15625.4799.671581.186354@argo.ozlabs.ibm.com
> That is indeed very strange. The first word should be non-zero at the
> very least. Is it possible that your program has in fact trashed its
> stack? Another thing to try would be to check the contents of
> current->user_stack_xxx immediately after you copy it to see whether
> it is all zero at that point.
Thank you all for the answer, it is now working fine.
I have basically used the LTT routine to analyze the EABI stack
frames, provided by Frank.
When I copy the relevant addresses (backchain pointer, saved link
register)
to separate static buffer and not to the task structure it is
working.
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/
prev parent reply other threads:[~2002-06-19 11:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 7:43 Accessing the user stack inside system call service routine Steffen Rumler
2002-06-13 11:10 ` 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 [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=3D106DC2.B50D7100@icn.siemens.de \
--to=steffen.rumler@icn.siemens.de \
--cc=frank_rowand@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=nhorman@lvl7.com \
--cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.