Hello Mikko,
Tried a bit more and finally got the log to work. It comes with journalctrl
itself.
Basically, we need to enable the debug log of Vehicle WRT itself.
This is what I tried.
1. Download the 'wrt-plugins-ivi-0.13.0-2.9.src.rpm'
2. Extract the source code
3. Added ADD_DEFINITIONS("-DTIZEN_ENGINEER_MODE") to to
'wrt-plugins-ivi-0.13.0/CMakeLists.txt'
4. Compile the 'wrt-plugins-ivi-0.13.0' again and install.
The 'TIZEN_ENGINEER_MODE' enabled the debug logs(LoggerD) only. Ideally the
LoggerI and LoggerE prints should come by default because they are defined
outside 'TIZEN_ENGINEER_MODE' macro.
Thanks & Regards,
- Ketan
On 21 February 2014 16:21, Ylinen, Mikko <[email protected]> wrote:
> Hi,
>
>
> On Thu, Feb 20, 2014 at 2:49 PM, Deshpande, Ketan <
> [email protected]> wrote:
>
>> Hello All,
>>
>> Thank you all for this information. Now I can get to see the system logs.
>> However, the issue I still face is I cannot see the 'Vehicle WRT plugin'
>> logs.
>>
>> For example, I can see the plugin loading messages and other system
>> messages, but none of 'Vehicle WRT Plugin' messages.
>>
>> To be more specific, We have a log defined in 'JSVehicle.cpp' that says,
>> LoggerD("JSVehicle::initialize ");
>>
>> This 'JSVehicle::initialize' cannot be seen in the log. Is there any
>> other/different setting for the same?
>>
>
> I've heard reports saying time same.
>
> Would you be able try the dlogutil+android logger option to see if it
> works with that?
>
> At the same time you can exercise the new logging HOWTO wiki page ;)
>
> Thanks,
> -- Mikko
>
>
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
