On 12/09/2011 09:45 AM, k...@ixxat.de wrote: > I am new to using trace, but I think this is the output you are looking for: > ... > canconfig-3288 [000] 3756.163033: can_fill_xstats <-rtnl_link_fill > canconfig-3288 [000] 3756.163034: can_fill_info <-rtnl_link_fill > canconfig-3288 [000] 3756.163041: can_fill_xstats <-rtnl_link_fill > canconfig-3288 [000] 3756.163042: can_fill_info <-rtnl_link_fill > canconfig-3288 [000] 3756.163047: can_fill_xstats <-rtnl_link_fill > canconfig-3288 [000] 3756.163048: can_fill_info <-rtnl_link_fill > canconfig-3288 [000] 3756.163066: can_fill_xstats <-rtnl_link_fill > canconfig-3288 [000] 3756.163067: can_fill_info <-rtnl_link_fill > canconfig-3288 [000] 3756.163073: can_fill_xstats <-rtnl_link_fill > canconfig-3288 [000] 3756.163073: can_fill_info <-rtnl_link_fill
Yep, I wanted to check if can_fill_info() is called at all. Actually, can_fill_info() does not return an error code so what I can think off is a mismatch in the data structure. What kernel CAN header files did you use when building libsocketcan? Next step would be to use "gdb" to find out where the error happend in the code. Most errors while print an error message, though. Wolfgang. _______________________________________________ Socketcan-core mailing list Socketcan-core@lists.berlios.de https://lists.berlios.de/mailman/listinfo/socketcan-core
