Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 20 Jul 2004 18:03:59 -0700
From:      Julian Elischer <julian@elischer.org>
To:        "Greg 'groggy' Lehey" <grog@freebsd.org>
Cc:        Andrew Gallatin <gallatin@cs.duke.edu>
Subject:   Re: Excellent job on the firewire support!
Message-ID:  <40FDC0FF.30901@elischer.org>
In-Reply-To: <20040721003850.GD78419@wantadilla.lemis.com>
References:  <16634.47272.768935.436137@grasshopper.cs.duke.edu> <200407182039.10773.dfr@nlsystems.com> <16634.54674.966908.540880@grasshopper.cs.duke.edu> <200407182104.53221.dfr@nlsystems.com> <87hds3pfgv.wl@tora.nunu.org> <20040721003850.GD78419@wantadilla.lemis.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Greg 'groggy' Lehey wrote:

>On Tuesday, 20 July 2004 at 11:41:52 +0900, Hidetoshi Shimokawa wrote:
>  
>
>>(sorry for resending)
>>
>>At Sun, 18 Jul 2004 21:04:53 +0100,
>>Doug Rabson wrote:
>>    
>>
>>>>2) Is dcons usable after a panic (ie, DDB or KDB_TRACE)?  Or is it
>>>>   only usable for remote-gdb?
>>>>        
>>>>
>>>Dcons provides two full duplex streams - one for console and one for
>>>gdb. You can use DDB on the console just like normal.
>>>      
>>>
>>It's designed for such panic/debugging situation.
>>Actually, it's rather inefficient for usual situation
>>but the speed of FireWire hide the problem ;-)
>>    
>>
>
>I think that the most spectacular use of firewire is debugging a
>completely hung system.  If you've already attached, the debugger can
>still access the memory of a system which isn't reacting *at all*.
>Obviously you can't continue execution, but just seeing what's in
>memory is a great advantage.
>
>On the other hand, it was my understanding that marcel's new kernel
>debugging framework broke firewire debugging.  What's the current
>status there?
>
He helped "Mr Firewire" get it going again the next day...

>
>Greg
>--
>Note: I discard all HTML mail unseen.
>Finger grog@FreeBSD.org for PGP public key.
>See complete headers for address and phone numbers.
>  
>




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40FDC0FF.30901>