From: "Sangmoon Kim" <dogoil@etinsys.com>
To: <linuxppc-embedded@lists.linuxppc.org>,
"Claus Gindhart" <Claus.Gindhart@pep.de>
Subject: Re: execve system call question
Date: Wed, 27 Feb 2002 10:45:00 +0900 [thread overview]
Message-ID: <008701c1bf30$72709200$1a11efcb@industrialDiv.hanasys.co.kr> (raw)
In-Reply-To: 21A8AE56EBB6D411A4520060973D360179DD48@pepintercom.pep.de
Hi Claus Gindhart
> I assume, that Your code is stuck inside the init process.
> There is an easy to way to find out, if my assumption is right.
> - Use a sash (Statically linked standalone shell) and replace /sbin/init
> with the executable.
> - If You get a prompt now, the execve works o.k, the hangup is inside init
>
> The further proceeding depends on the result of the above test.
>
I tried other thing like /bin/bash and 'hello world' things. but it didnot worked.
Thank you!
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-02-27 1:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <21A8AE56EBB6D411A4520060973D360179DD48@pepintercom.pep.de>
2002-02-27 1:45 ` Sangmoon Kim [this message]
[not found] <C08678384BE7D311B4D70004ACA371050B7632EF@amer22.avnet.com>
2002-03-04 1:20 ` execve system call question Sangmoon Kim
2002-02-27 14:33 Derrik Weeks
2002-03-04 1:11 ` Sangmoon Kim
[not found] <C08678384BE7D311B4D70004ACA371050B7632EC@amer22.avnet.com>
2002-02-27 1:48 ` Sangmoon Kim
[not found] <69BCCDDC980B4641BFC908D7BF95F1842A4B89@exchsrv-eng>
2002-02-27 1:41 ` Sangmoon Kim
-- strict thread matches above, loose matches on Subject: below --
2002-02-26 14:34 Derrik Weeks
2002-02-27 1:31 ` Sangmoon Kim
2002-02-26 9:16 monitor in mpc860fads gao xiaoguo
2002-02-26 10:35 ` execve system call question Sangmoon Kim
2002-02-26 13:11 ` None Atall
2002-02-27 1:21 ` Sangmoon Kim
2002-02-27 7:54 ` Wolfgang Denk
2002-02-26 13:21 ` Wolfgang Denk
2002-02-27 1:36 ` Sangmoon Kim
2002-02-26 13:27 ` Christian Pellegrin
2002-02-27 1:23 ` Sangmoon Kim
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='008701c1bf30$72709200$1a11efcb@industrialDiv.hanasys.co.kr' \
--to=dogoil@etinsys.com \
--cc=Claus.Gindhart@pep.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).