From: Wolfgang Grandegger <wg-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
To: kime-Z4QKGCRq86k@public.gmane.org
Cc: socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org,
linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: CAN State Information
Date: Fri, 09 Dec 2011 10:00:27 +0100 [thread overview]
Message-ID: <4EE1CE2B.6090909@grandegger.com> (raw)
In-Reply-To: <166589D0B9DD2547A1319599B9BADA1FC1998A-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
On 12/09/2011 09:45 AM, kime-Z4QKGCRq86k@public.gmane.org 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.
next prev parent reply other threads:[~2011-12-09 9:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <166589D0B9DD2547A1319599B9BADA1FC1960C@vsv-exchange.ixxat.intranet.priv>
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1960C-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-06 15:26 ` CAN State Information Wolfgang Grandegger
[not found] ` <4EDE342E.8030102-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-06 18:54 ` Wolfram Sang
2011-12-08 8:43 ` kime-Z4QKGCRq86k
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1981F-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-08 19:15 ` Wolfgang Grandegger
2011-12-09 8:03 ` kime
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC19968-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09 8:15 ` Wolfgang Grandegger
[not found] ` <4EE1C3BF.70104-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09 8:19 ` Wolfgang Grandegger
[not found] ` <4EE1C47A.7080507-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-09 8:45 ` kime-Z4QKGCRq86k
[not found] ` <166589D0B9DD2547A1319599B9BADA1FC1998A-F+3lUZ2EnXJqWLKVXlbt41Kd6C4pVHazbKV4uwnAPJ4@public.gmane.org>
2011-12-09 9:00 ` Wolfgang Grandegger [this message]
2011-12-09 13:41 ` kime
2011-12-09 14:49 ` Wolfgang Grandegger
[not found] ` <4EE2200E.4060403-5Yr1BZd7O62+XT7JhA+gdA@public.gmane.org>
2011-12-12 10:21 ` kime-Z4QKGCRq86k
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE1CE2B.6090909@grandegger.com \
--to=wg-5yr1bzd7o62+xt7jha+gda@public.gmane.org \
--cc=kime-Z4QKGCRq86k@public.gmane.org \
--cc=linux-can-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=socketcan-core-0fE9KPoRgkgATYTw5x5z8w@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).