Re: rump newbie question

[Justin Cormack <justin%specialbusservice.com@localhost>]

On Tue, Feb 18, 2014 at 12:33 PM, Patrick Welche <prlw1%cam.ac.uk@localhost> 
wrote:
> As I am having issues with kgdb over serial, I thought I would try kernel
> debugging using rump. My first attempt has been to run rump_allserver, and
>
> (gdb) attach 24469
> Attaching to program: /usr/bin/rump_allserver, process 24469
> Reading symbols from /usr/lib/librumpdev_audio.so.0...done.
> Loaded symbols for /usr/lib/librumpdev_audio.so.0
> ...
> (gdb) break sys_modctl
> Breakpoint 1 at 0x7f7fe6c49971: file 
> /usr/src/lib/librump/../../sys/rump/../kern/sys_module.c, line 111.
> (gdb) c
> Continuing.
>
>
> Then:
>
> quark# rump.modload /stand/amd64/6.99.31/modules/hdaudio/hdaudio.kmod
> rump.modload: prog init failed: No such file or directory
>
> Is this a sensible way of looking at hdaudio? What am I missing?

Looking at ktrace on my machine it loads hdaudio fine but then fails
trying to  open /stand/amd64/6.99.28/modules/pci , not sure if you
have the same issue, what does ktrace output say?

Justin