Understanding LTT

I am looking at LTT as a good starting point to recording traces for
post-crash analysis. Unlike what most people are doing, I am developing
for an embedded system which has no place to store a crash dump. My
approach is to write the traces to "reserved" memory that won't be
cleared when the system comes back up. To do this, it looks like the
approach would be to use flight recorder mode on buffers allocated in
the reserved areas. Trying to figure out where to splice into LTT to do
this, however, is somewhat time-consuming as there is less documentation
in the code than I would prefer. From what I can gather, the LTT code
looks designed so that it might accommodate a new transport layer that I
could write to do while I want.
 
Is there documentation on LTT buffer allocation outside of the code to
which I might refer, or can someone give me a few tips on where to
start? Alternatively, is there a better approach that someone can think
of?
 
--
David VomLehn, Staff O/S Software Engineer
Scientific Atlanta, A Cisco Company
10590 N. Tantau Avenue, Cupertino, CA 95014
[email protected] <mailto:[email protected]> 
voice: 408-777-5052 fax: 408-777-0176
 
 




     - - - - - Appended by Scientific Atlanta, a Cisco company - - - - -         
This e-mail and any attachments may contain information which is confidential, 
proprietary, privileged or otherwise protected by law. The information is solely 
intended for the named addressee (or a person responsible for delivering it to 
the addressee). If you are not the intended recipient of this message, you are 
not authorized to read, print, retain, copy or disseminate this message or any 
part of it. If you have received this e-mail in error, please notify the sender 
immediately by return e-mail and delete it from your computer.

_______________________________________________
Ltt-dev mailing list
[email protected]
http://listserv.shafik.org/mailman/listinfo/ltt-dev