$
Ktrace'ing the process and seeing with my own eyes what was going on, seemed like a good idea.
-Here comes the fun. I misread the ktrace(1) man page and typed:
+Here comes the fun. I misread the [ktrace(1)](http://leaf.dragonflybsd.org/cgi/web-man?command=ktrace§ion=1) man page and typed:
$ ktrace -c ./t_aio
Stopped at 0x80aca52: movl 0(%eax),%eax
db>
-This db> prompt is from ddb(4), the interactive kernel debugger.
+This db> prompt is from [ddb(4)](http://leaf.dragonflybsd.org/cgi/web-man?command=ddb§ion=4), the interactive kernel debugger.
The
fault virtual address = 0x0
# Gdb
-Quoting from vkernel(7):
+Quoting from [vkernel(7)](http://leaf.dragonflybsd.org/cgi/web-man?command=vkernel§ion=7):
It is possible to directly gdb the virtual kernel's process. It is recommended that you do a `handle SIGSEGV noprint' to ignore page faults processed by the virtual kernel itself and `handle SIGUSR1 noprint' to ignore signals used for simulating inter-processor interrupts (SMP build only).