From: Elias Athanasopoulos <eathan@otenet.gr>
To: jnf <xjnfx@doityourself.com>
Cc: linux-c-programming@vger.kernel.org
Subject: Re: sock-ops->connect()
Date: Sun, 6 Oct 2002 17:36:36 +0300 [thread overview]
Message-ID: <20021006173636.C3197@neutrino.particles.org> (raw)
In-Reply-To: <20021006101521.B253E11E0B@sitemail.everyone.net>; from xjnfx@doityourself.com on Sun, Oct 06, 2002 at 03:15:21AM -0700
On Sun, Oct 06, 2002 at 03:15:21AM -0700, jnf wrote:
> struct socket *sock;
> struct sockaddr_in adr;
> int err,port;
>
> // ...
>
> port = 5260;
>
> err = sock_create(AF_INET,SOCK_STREAM,IPPROTO_TCP,&sock);
I'm not very familiar with kernel internals, but I think you don't
seem to allocate space for the sock structure.
Elias
--
http://gnewtellium.sourceforge.net MP3 is not a crime.
next prev parent reply other threads:[~2002-10-06 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-06 10:15 sock-ops->connect() jnf
2002-10-06 14:36 ` Elias Athanasopoulos [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-07 10:51 sock-ops->connect() jnf
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=20021006173636.C3197@neutrino.particles.org \
--to=eathan@otenet.gr \
--cc=linux-c-programming@vger.kernel.org \
--cc=xjnfx@doityourself.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 NNTP newsgroup(s).