you can gdb -k mykernel /dev/mem
and do
list bqrelse+0x25
(I think)
alternatively,
in ddb you can do:
x/iiiiiiiiiiiiiiiiiii bqrelse
and work out what is wrong by reading the machine instructions
WHen I have one machine I usually debug by running the new kernel
within a VMWARE virtual machine. Using the nmdm driver
you can run gdb in the main machine to debug it, all within one machine.
(unfortunatly it doesn't help for debugging drivers because the virtual
machine doesn't have acces to the real hardware).
On Wed, 5 Sep 2001, Zhihui Zhang wrote:
>
> I know gdb can source stepping the kernel. But without two machines, you
> can not do it. Now I have only one machine and the system panic:
>
> db> trace
> bqrelse(cxxx, cxxx, cxxx, cxxxx, cxxx) at bqrelse+0x25
>
> is there a way to use these addresses to figure out which line or lines of
> source are suspect to cause the panic? Thanks.
>
> Regards,
>
> -Zhihui
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-hackers" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message