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 debugging
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 my SMP test
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
3 matches
Mail list logo
