On Sun, Mar 28, 2010 at 7:59 PM, John David Anglin <dave@xxxxxxxxxxxxxxxxxx> wrote: >> I know it's easier to debug a static application for these cases, so I >> think a fixed glibc will help. > > Yes. > > It's proving more difficult than I thought to fix the kernel and > I'm not sure I understand how this works: > > LDREG TI_TASK-THREAD_SZ_ALGN-FRAME_SIZE-FRAME_SIZE(%r30), %r1 > LDREG TASK_PT_GR19(%r1),%r2 > b wrapper_exit > copy %r0,%r28 > > It appears the child has to access the parent's pt_regs struct > to load the return for the child. I see that copy_process in do_fork will give the child a copy of the entire pt_reg structure so it has access to these values anyway? >> * What prevents the execve from returning to userspace? > > I presume you mean the caller's userspace. Yes, the process that calls execve. Cheers, Carlos. -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
