[BusyBox] busybox SegFaults

[David Douthitt]

On 30 Jan 2001, at 4:05, David Douthitt wrote:

> I've tried:
> 
> * Linux 2.2.19pre7
> * Linux 2.2.18
> * Openwall v1 for 2.2.18
> * Openwall v2 for 2.2.18
> * Busybox 0.47
> * Busybox 0.48
> * Busybox 0.49 (CVS)
> 
> I'm getting exasperated - this is a stumper for sure.
> 
> Next I'm going to try and turn "off" the Openwall patch security and 
> see what happens.  Then I'll try removing libsafe.  If I get really 
> desperate I'll change glibc to that included with Debian 2.1.

I tried using the EigerStein 2.2.16 kernel with VPN+Masq patches; 
this kernel does not have Openwall in it.  No change.

Removed libsafe again (renamed ld.so.preload to ld.so.preload2) - 
no change.

I checked the glibc in the system with that of one that works; no 
difference.  I haven't switched it in practice yet, but I did package it 
up (443k) if someone wants to try it.

Also, "gdb insmod" segfaults immediately (untrapped).

"insmod" does NOT segfault, but "insmod <anyopt>" does 
Segfault...

This is rather unusual, seems to me, since glibc hasn't changed in 
a long time; only the kernel changes, and busybox occasionally.  
SOMETHING is interfering and I'll be durned if I know what.

Could it be some kind of "interaction" in the busybox group of apps?

What else can it be?  I'm running out of ideas.

I tried a working busybox from another system - and it too 
SegFaulted.  I don't know what to do next.... busybox, the kernel, 
Openwall, VPN+Masq, Linux 2.2.18, Linux 2.2.16, Linux 2.2.19, 
seem to have all been cleared.  Even glibc doesn't seem to be 
suspect, since it is working elsewhere.  What is it?

-- 
David Douthitt
UNIX Systems Administrator
HP-UX, Linux, Unixware
n9ubh at callsign.net