Re: Tracking a bug in x86-64

[Bongani Hlope <bonganilinux@mweb.co.za>]

On Tuesday 14 June 2005 10:27 pm, Andrew Morton wrote:
> Linus Torvalds <torvalds@osdl.org> wrote:
> >
> > The way to do the binary searach is to get the
> >  	ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm1/2.6.11-mm1-broken-out.tar.gz 
> >  file, and then to apply half of the patches
> 
> Or:
> - install https://savannah.nongnu.org/projects/quilt/
> 
> cd /usr/src/linux
> wget ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11/2.6.11-mm1/2.6.11-mm1-broken-out.tar.gz
> tar xfz 2.6.11-mm1-broken-out.tar.gz
> mv broken-out patches
> mv patches/series .
> 
> Now you can do `quilt push 100' to apply 100 patches, `quilt pop 50' to
> remove half of them, etc.
> 
> Open a copy of the series file in an editor and add markers to it as you
> proceed through the search so you don't get lost.
> 

Hi

I've used quilt to et to the patch that is causing problems (quilt is great thanx Andrew). This is the sequence, which led me to
the possible culprit:
push 410, pop 205, pop 103, push 103, pop 51, pop 26, push 13, pop 6, push 4 and push 1
This points to: randomisation-top-of-stack-randomization.patch

Regards
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/