> p_emul is const, so it's not a very good candidate. choosing p_vmspace
> is just adding an emulation specific stuff in uvm, it's not very clean.
> There is p_emuldata, but I'm not sure about how to use it. On what
> should it point?

I thought a bit about it: p_vmspace seems the good place. After all, we
might want show a consistent break address to all processes, not only
Linux ones. We can keep track the break address as seen by the process
here. The real break address is beyond, page aligned, and we already
keep track of it in p_vmspace.

--=20
Emmanuel Dreyfus.
"L'achitecture x86 est impossible =E0 aimer." (John Hennessy)
p99dreyf@criens.u-psud.fr