linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sangmoon Kim" <dogoil@etinsys.com>
To: "linuxppc-embedded" <linuxppc-embedded@lists.linuxppc.org>
Subject: execve system call question
Date: Tue, 26 Feb 2002 19:35:04 +0900	[thread overview]
Message-ID: <008901c1beb1$409cc7f0$1a11efcb@industrialDiv.hanasys.co.kr> (raw)
In-Reply-To: 003101c1bea6$52edcf90$6801a8c0@gaoxg


Hi!
I'm debugging a custom MPC755 board
with linuxppc_devel from montavista rsync,
and /opt/hardhat/devkit/ppc/7xx/target for NFS root.
It booted and stoped after the message.

--------------------------------------------------------
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 1024 buckets, 8Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
IP-Config: Complete:
      device=eth0, addr=203.239.17.200, mask=255.255.255.0, gw=203.239.17.57,
     host=dogoil, domain=, nis-domain=(none),
     bootserver=203.239.17.57, rootserver=203.239.17.57, rootpath=
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 203.239.17.57
Looking up port of RPC 100005/1 on 203.239.17.57
VFS: Mounted root (nfs filesystem).
Freeing unused kernel memory: 76k init
--------------------------------------------------------

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.

Is there any method to debug this?
I'm debugging it for a month.

Please help me.

- Sangmoon Kim -

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

  reply	other threads:[~2002-02-26 10:35 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 ` Sangmoon Kim [this message]
2002-02-26 13:11   ` execve system call question 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
  -- 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='008901c1beb1$409cc7f0$1a11efcb@industrialDiv.hanasys.co.kr' \
    --to=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).