Re: [Valgrind-developers] Porting valgrind to FreeBSD

[Jeremy F. <je...@go...>]

On Sun, 2003-12-28 at 06:43, Doug Rabson wrote:
> It seems to me that the simplest approach would be to move the really
> os-dependant files into a subdir of coregrind (e.g. coregrind/linux).
> Files which seem to be in this category are vg_libpthread*.c,
> vg_procselfmaps.c, vg_proxylwp.c, vg_signals.c (maybe), vg_syscall.S,
> vg_syscalls.c, vg_unistd.h, vg_unsafe.h. Similarly in include,
> vg_kerneliface.h would move to include/linux/vg_kerneliface.h.

Yes, but I think we should take the time to break it down further.  Some
of those files are just Linux-dependent (like most of proxylwp.c, most
of vg_syscalls.c, procselfmaps.c, etc), and some are both linux-x86
dependent (*.S, vg_kerneliface.c, and so on).

Is FreeBSD x86 only, or has it been ported to other architectures (I
know the other BSDs are widely ported).  Do you know if all the BSDs
have, for example, common syscall numbers across architectures?

I'd be really interested if you can update the port for the FV world. 
I'd like to know where the new non-portable bits are.  For example, how
does FreeBSD lay out the user address space, and how much is reserved
for the kernel?

	J