From: Wolfgang Denk <wd@denx.de>
To: "Sangmoon Kim" <dogoil@etinsys.com>
Cc: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: execve system call question
Date: Tue, 26 Feb 2002 14:21:26 +0100 [thread overview]
Message-ID: <20020226132131.B2A58109E3@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 26 Feb 2002 19:35:04 +0900." <008901c1beb1$409cc7f0$1a11efcb@industrialDiv.hanasys.co.kr>
In message <008901c1beb1$409cc7f0$1a11efcb@industrialDiv.hanasys.co.kr> you wrote:
>
> I traced the code and the point of stopping is after calling
> execve("/sbin/init", argv_init, envp_init)
> in init/main.c
>
> I was trying to trace more, but it was impossible
> because of the complexity of the code.
It's not impossible. In fact, it's quite simple.
You're running with root filesystem over NFS, so just start up a
network sniffer (like ethereal) and check all NFS requests and
replys. Probably something is missing in your root filesystem.
Something essential, like /dev/console or so.
> Is there any method to debug this?
Yes, attach a BDI2000 and check where you are...
> I'm debugging it for a month.
Urghhh...
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Use C++ to confuse your enemies; use C to produce stable code.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-26 13:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2002-02-27 1:36 ` Sangmoon Kim
2002-02-26 13:27 ` Christian Pellegrin
2002-02-27 1:23 ` 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
[not found] <69BCCDDC980B4641BFC908D7BF95F1842A4B89@exchsrv-eng>
2002-02-27 1:41 ` Sangmoon Kim
[not found] <21A8AE56EBB6D411A4520060973D360179DD48@pepintercom.pep.de>
2002-02-27 1:45 ` Sangmoon Kim
[not found] <C08678384BE7D311B4D70004ACA371050B7632EC@amer22.avnet.com>
2002-02-27 1:48 ` Sangmoon Kim
2002-02-27 14:33 Derrik Weeks
2002-03-04 1:11 ` Sangmoon Kim
[not found] <C08678384BE7D311B4D70004ACA371050B7632EF@amer22.avnet.com>
2002-03-04 1:20 ` 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=20020226132131.B2A58109E3@denx.denx.de \
--to=wd@denx.de \
--cc=dogoil@etinsys.com \
--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).