[uClibc]busybox segfaults (but is it busybox?)

Agust Karlsson Gusti at pallas.dk
Mon Mar 24 15:04:43 UTC 2003

Are you running ash as a shell?
I experienced the same problem with ash and changed to msh, solved that problem but introduced some others like unability to run a shell script directly.

Agust Karlsson            mailto:gusti at pallas.dk
Pallas Informatik A/S     http://www.pallas.dk
Allerød Stationsvej 2D    Tel.: +45 48 10 24 10
DK-3450 Allerød           Fax.: +45 48 10 24 01

> -----Original Message-----
> From:	Klaas van Gend [SMTP:klaas.vangend at reduct.net]
> Sent:	Monday, March 24, 2003 3:46 PM
> To:	uclibc at uclibc.org
> Subject:	[uClibc]busybox segfaults (but is it busybox?)
> Hi!
> I'm using kernel 2.4.20, Busybox 0.60.5 and uClibc 0.9.19.
> These are all compiled using the latest root_fs building system.
> The target stuff is run on an AMD elan-520 processor with 32 MB RAM.
> All goes well during startup, but if an insmod fails, it segfaults.
> As a matter of fact, *every* failure (thus not just insmod) crashes the 
> shell and its parents...
> This is not good.
> It is also the case if I boot from the Linux-Bootable Business Card 
> CD-ROM and then chroot to /dev/hda1. busybox segfaults on error and I 
> leave the chroot...
> I can't find any info on this on the mailing lists and I'm at a loss on 
> where to start debugging this... Is it Busybox or is it uclibc or ???
> Any hints are appreciated!
> Yours,
> Klaas van Gend
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc

More information about the uClibc mailing list