From: Jerry Van Baren <vanbaren_gerald@si.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Hung inside execve
Date: Tue, 26 Nov 2002 16:03:43 -0500 [thread overview]
Message-ID: <5.1.0.14.2.20021126155728.02406c88@falcon.si.com> (raw)
In-Reply-To: <20021126204034.87211C614B@atlas.denx.de>
At 09:40 PM 11/26/2002 +0100, Wolfgang Denk wrote:
>In message <B0CD235912AED411B69800D0B7C9F60F1DF88A@mail> you wrote:
> >
> > I have been going through the LinuxPPC archives, looking for answers to my
> > problem, but still could not proceed ahead. My problem is that the Linux
> > will hang after the line 'execve("bin/sh", argv_init, envp_init);' inside
> > the init function of the file main.c. I have added the printk statements
> > preceding each of the execve calls. The last prink should be right before
> > the panic statement but it did not get executed, therefore I suspect that
> > the culprit is 'execve("bin/sh", argv_init, envp_init);' .
For what it is worth, my first thought when I saw this is that you probably
have a shared library missing on your RAM disk. As suggested by Wolfgang,
use NFS and see where your system stops requesting files and what file it
(probably) was unable to find. You can use binutils & company to figure
out what symbols/libraries are needed by /bin/sh, but it is generally
easier to just run it using NFS and sniff the ether.
>Ummm... in situations like this life is _much_ easier when you can
>use a debugger. Get yourself a BDI2000!
BDI-2000: better than chicken soup for whatever ails you ;-)
gvb
[lots more good advice snipped]
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-11-26 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 19:55 Hung inside execve Francis Yu <francisy@luxn.com>
2002-11-26 20:40 ` Wolfgang Denk
2002-11-26 21:03 ` Jerry Van Baren [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 21:23 Rod Boyce
[not found] <B0CD235912AED411B69800D0B7C9F60F1DF8A7@mail>
2002-12-09 20:55 ` Wolfgang Denk
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=5.1.0.14.2.20021126155728.02406c88@falcon.si.com \
--to=vanbaren_gerald@si.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).