find / rm corrupting memory

[Mike Frysinger]

On Saturday 26 January 2008, Roy Marples wrote:
> On Saturday 26 January 2008 17:01:26 walter harms wrote:
> > Roy Marples wrote:
> > > Hi List.
> > >
> > > I'm trying to track down a memory corruption when using the following
> > >
> > > /tmp/bb $ touch a b
> > > /tmp/bb $ find . -type f -exec rm -rf -- {} \;
> > > /tmp/bb $ touch a b c
> > > /tmp/bb $ find . -type f -exec rm -rf -- {} \;
> > > rm: invalid option --
> > > BusyBox v1.9.0 (2008-01-25 14:43:46 GMT) multi-call binary
> >
> > works for me:
> >
> > ~/src/busybox/busybox-1.9.0/check> touch a b
> > /check> ../busybox find . -type f -exec rm -rf -- {} \;
> > /check> ll
> > insgesamt 0
> > /check> touch a b c
> > /check> ../busybox find . -type f -exec rm -rf -- {} \;
> > /check> ll
> > insgesamt 0
> >
> > what version of gcc you are using ?
>
> gcc (GCC) 4.2.2 (Gentoo 4.2.2 p1.0)
> Interestingly I cannot replicate it on my amd64, but can on my i386 :/

it'd be easier to debug i think if we could reduce the # of config options in 
play.  the default config Gentoo uses is a beast as busybox is installed on 
all systems as a rescue shell.  then we could try to apply HTB or SSP or 
mudflap techs and see how it goes ...
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: This is a digitally signed message part.
Url : http://lists.busybox.net/pipermail/busybox/attachments/20080126/a263c31f/attachment-0002.pgp