From: Wolfgang Grandegger <wg@domain.hid>
To: rolandtollenaar@domain.hid
Cc: xenomai-help <xenomai@xenomai.org>
Subject: Re: [Xenomai-help] rtcan bufferoverflow but no evidence
Date: Mon, 13 Aug 2007 22:07:19 +0200 [thread overview]
Message-ID: <46C0B9F7.9060103@domain.hid> (raw)
In-Reply-To: <46C0B1DF.6090509@domain.hid>
Roland Tollenaar wrote:
> Hi Wolfgang,
>
>>> See below. This does not look good. Does it mean that I am only
>>> always reading out the last socket and the rest are having their
>>> buffers pumped full? Should I be unbinding somehow?
>>
>> Don't know, check your code ;-).
> Thanks that is exactly what I did because I thought I was unbinding.
> rt_dev_close () should do that for me correct? Its not. At least not
> reliably. :(
That's wired. You mean you called rt_dev_close() and the socket still
does show up in /proc/rtcan_sockets? Is it possible that there is
another task still using that socket? Could you show the code fragment
doing that.
Wolfgang.
next prev parent reply other threads:[~2007-08-13 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 14:58 [Xenomai-help] rtcan bufferoverflow but no evidence Roland Tollenaar
2007-08-13 15:38 ` Wolfgang Grandegger
[not found] ` <46C07D73.7070302@domain.hid>
[not found] ` <46C080C8.10906@domain.hid>
[not found] ` <46C0835E.8010105@domain.hid>
[not found] ` <46C0B036.3030306@domain.hid>
[not found] ` <46C0B1DF.6090509@domain.hid>
2007-08-13 19:59 ` Wolfgang Grandegger
2007-08-13 20:20 ` Roland Tollenaar
2007-08-13 20:07 ` Wolfgang Grandegger [this message]
2007-08-13 22:09 ` Jan Kiszka
2007-08-14 5:20 ` Roland Tollenaar
2007-08-14 7:24 ` Jan Kiszka
2007-08-14 6:46 ` Wolfgang Grandegger
2007-08-14 7:41 ` Roland Tollenaar
2007-08-14 7:52 ` Jan Kiszka
2007-08-14 10:34 ` Roland Tollenaar
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=46C0B9F7.9060103@domain.hid \
--to=wg@domain.hid \
--cc=rolandtollenaar@domain.hid \
--cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.