From: Andrew Lunn <andrew@lunn.ch>
To: Will Lentz <will_lentz@trimble.com>
Cc: Hans H?bner <hans@huebner.org>, ecos <ecos-discuss@ecos.sourceware.org>
Subject: Re: [ECOS] uipc_socket.c (and cyg_tcp_maxidle)
Date: Fri, 17 Jun 2005 07:15:00 -0000 [thread overview]
Message-ID: <20050617071434.GA4778@lunn.ch> (raw)
In-Reply-To: <1118965523.18774.24.camel@localhost.localdomain>
On Thu, Jun 16, 2005 at 04:45:23PM -0700, Will Lentz wrote:
> Hi Hans,
>
> No problem :-). I'm forwarding this on to the list so others know it
> helps.
>
> BTW - any comments from people? In uipc_socket.c soalloc() the
> zalloci() is assigned to "so", so it looks right to do the zfreei() on
> "so".
There has been problems like this in the past because of the missing
userspace/kernel space transition which FreeBSD has but eCos does not
have. Im out on a customer visit at the moment so don't have the
oportunity to look at this now, but i will take a look once im back.
This things are normally very easy to fix if its what i think it is.
Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2005-06-17 7:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 22:39 [ECOS] uipc_socket.c Will Lentz
2005-06-16 7:06 ` [ECOS] uipc_socket.c (and cyg_tcp_maxidle) Hans Hübner
2005-06-16 15:36 ` Will Lentz
2005-06-16 15:51 ` Hans Hübner
2005-06-16 16:06 ` Will Lentz
[not found] ` <20050616183534.N69813@web.m68k.de>
2005-06-16 23:45 ` Will Lentz
2005-06-17 7:15 ` Andrew Lunn [this message]
2005-06-17 20:12 ` Andrew Lunn
2005-06-17 21:00 ` Will Lentz
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=20050617071434.GA4778@lunn.ch \
--to=andrew@lunn.ch \
--cc=ecos-discuss@ecos.sourceware.org \
--cc=hans@huebner.org \
--cc=will_lentz@trimble.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).