> Tried both,
> 
> BUT for example at any time I got after execution that ran well:
> uvm_fault(..., 0, 1) -> e
> kernel: page fault trao, code=0
> Stopped in pid 10 (ioflush) at ffs_sync+0x7b: testb $ox1f, 0x38(%eax)
> 
> Eric.

The message/panic uvm_fault(..) is just the kernel equivalent 
to a segmentation fault.

It just means that you are overwriting memory somewhere that
does not belong to you, free memory multiple times ...

	Stephan