[genivi-dlt] DLT usage inside shared library
Lipka, Christoph (ADITJ/SWG)
clipka at jp.adit-jv.com
Thu May 26 00:54:51 EDT 2016
We currently use DLT also for logging and control the log output inside a library that is used by several applications. Some of these applications use DLT, others not.
This results in some problems which we have solved in a way that we added a new API inside DLT User Library to check if a APID is already defined. If this is not the case, we create an APID with a predefined name inside the library for that process (this happens for applications that does not use DLT on their own) otherwise the applications APID remains untouched.
Drawback of this solution is that we cannot distinguish from which non-DLT applications a log came if more than one application using this library but not DLT. Also controlling might only possible for the latest created application. Therefore a way is needed to "generate" an unique APID for non-DLT processes inside the shared library. One way might be to "ask" the Daemon for a unique APID, or store a starting APID (like "A000" somewhere in the RFS which is updated every time a new "anonymous" application registers at DLT. (like "A001", "A002" ...)
As described above, our current solution has some drawbacks we have to solve, if possible directly in a way that might be acceptable by community. So the question is if anyone has a similar use case/problem? Is this something that might be added to GENIVI DLT in future?
Advanced Driver Information Technology
Software Group (ADITJ/SWG)
1-1 Showa-cho, Kariya-shi
Aichi-ken 448-8661, Japan
Tel. +81-(0)566 61-5124
Fax +81-(0)566 25-4774
clipka at jp.adit-jv.com<mailto:clipka at jp.adit-jv.com>
ADIT is joint venture company of DENSO Corporation and Bosch GmbH
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the genivi-diagnostic-log-and-trace