From: Magnus Hjorth <mh@omnisys.se>
To: Daniel Ng <daniel_ng11@lycos.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: ELDK glibc fcntl(socketFd, F_SETFL, flags) causes Seg Fault
Date: Fri, 02 Feb 2007 16:03:55 +0100 [thread overview]
Message-ID: <45C352DB.8070409@omnisys.se> (raw)
In-Reply-To: <loom.20070201T073939-302@post.gmane.org>
Daniel Ng wrote:
> Hi,
>
> My application Seg Faults when I try to set flags for my socket fd.
>
> Then I try getting the fd flags:
> fcntl(fd, F_GETFL, flags)
>
Shouldn't it be &flags ??
--
Magnus Hjorth, M.Sc.
Omnisys Instruments AB
Gruvgatan 8
SE-421 30 Västra Frölunda, SWEDEN
Phone: +46 31 734 34 09
Fax: +46 31 734 34 29
http://www.omnisys.se
next prev parent reply other threads:[~2007-02-02 15:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 6:56 ELDK glibc fcntl(socketFd, F_SETFL, flags) causes Seg Fault Daniel Ng
2007-02-02 7:30 ` Wolfgang Denk
2007-02-05 3:11 ` Daniel Ng
2007-02-02 14:11 ` ELDK glibc fcntl(socketFd,F_SETFL, " Edward Jubenville
2007-02-02 15:03 ` Magnus Hjorth [this message]
[not found] <mailman.1565.1170401421.9285.linuxppc-embedded@ozlabs.org>
2007-02-02 14:10 ` ELDK glibc fcntl(socketFd, F_SETFL, " Christopher Dumoulin
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=45C352DB.8070409@omnisys.se \
--to=mh@omnisys.se \
--cc=daniel_ng11@lycos.com \
--cc=linuxppc-embedded@ozlabs.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).