On Wed, 5 Sep 2001, Zhihui Zhang wrote:
>
>
> On Wed, 5 Sep 2001, Julian Elischer wrote:
> >
> > 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 ma
On 29-Mar-01 John Baldwin wrote:
>
> On 29-Mar-01 Alfred Perlstein wrote:
>> I can't seem to get a crashdump, is there a way to take a
>> ddb crash address: "Stopped at lf_setlock+0x52"
>> and boot later and see what line of code that's on?
>
> l *lf_setlock+0x52
>
> For example, on one of m
On 29-Mar-01 Alfred Perlstein wrote:
> I can't seem to get a crashdump, is there a way to take a
> ddb crash address: "Stopped at lf_setlock+0x52"
> and boot later and see what line of code that's on?
l *lf_setlock+0x52
For example, on one of my SMP test boxes:
> gdb -k /sys/compile/MUTEX/ke
In article <[EMAIL PROTECTED]>,
Alfred Perlstein <[EMAIL PROTECTED]> wrote:
> I can't seem to get a crashdump, is there a way to take a
> ddb crash address: "Stopped at lf_setlock+0x52"
> and boot later and see what line of code that's on?
Assuming you have a corresponding kernel with debuggin
On Wed, 28 Mar 2001, Alfred Perlstein wrote:
> I can't seem to get a crashdump, is there a way to take a
> ddb crash address: "Stopped at lf_setlock+0x52"
> and boot later and see what line of code that's on?
I do *lots* of debugging on very old 2.2.2 version stuff for my company,
and I have a
I can't seem to get a crashdump, is there a way to take a
ddb crash address: "Stopped at lf_setlock+0x52"
and boot later and see what line of code that's on?
--
-Alfred Perlstein - [[EMAIL PROTECTED]|[EMAIL PROTECTED]]
Instead of asking why a piece of software is using "1970s technology,"
sta
6 matches
Mail list logo
