Re: [Qemu-devel] Armv5 target

[Ulrich Hecht]

Hi!

On Wednesday 02 February 2005 16:47, Paul Brook wrote:
> On Wednesday 02 February 2005 12:01, Lennert Buytenhek wrote:
> > On Wed, Feb 02, 2005 at 01:26:37AM +0000, Paul Brook wrote:
> > > > > +    /* XXX: locking issue */
> > > > > +    if (is_write && page_unprotect(address, pc, puc)) {
> > > > > +        return 1;
> > > > > +    }
> > > > >      /* XXX: do more */
> > > > >      return 0;
> > > > >  }
> > > >
> > > > Sort of. Self-modifying code (e.g. stack trampolines) are still
> > > > broken, and the patch above should work.
> > > >
> > > > However I just tested it and it doesn't seem to work any more.
> > > > It seems that the SEGV handler is being passed an address of 0,
> > > > rather than the actual faulting location.
> > > >
> > > > This may be a host kernel/libc bug.
> > >
> > > I just tried on a few different machines, and this is a host
> > > kernel bug specific to one particular kernel (custom 2.6.9).
> >
> > Do you have some example code that demonstrates this?
>
> I've attached two programs. segv-test.c tests for the kernel bug.

This program hangs in an endless segfault loop when I run it in qemu-arm. 
The kernel version does not seem to matter here, I have tried 2.6.11, 
2.6.5 and 2.4.21. Has anybody ever observed this and/or knows what it is 
caused by? (The test works fine on i386 and on a real ARM machine.)

CU
Uli