This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Broken connect syscall invocation ?
- From: Artem Polyakov <artemp at mellanox dot com>
- To: Jonathan Wakely <jwakely at redhat dot com>
- Cc: "gcc-bugs at gcc dot gnu dot org" <gcc-bugs at gcc dot gnu dot org>
- Date: Thu, 26 May 2016 08:40:07 +0000
- Subject: Re: Broken connect syscall invocation ?
- Authentication-results: sourceware.org; auth=none
- Authentication-results: redhat.com; dkim=none (message not signed) header.d=none;redhat.com; dmarc=none action=none header.from=mellanox.com;
- References: <AM4PR05MB16983FC571D1F0D2AB0A25E6BA410 at AM4PR05MB1698 dot eurprd05 dot prod dot outlook dot com>,<20160526083901 dot GA15645 at redhat dot com>
- Spamdiagnosticmetadata: NSPM
- Spamdiagnosticoutput: 1:23
Thank you. Will move there.
----
Best regards, Artem Y. Polyakov
HPC Engineer, Mellanox Ltd.
â
________________________________________
ÐÑ: Jonathan Wakely <jwakely@redhat.com>
ÐÑÐÑÐÐÐÐÐÐ: 26 ÐÐÑ 2016 Ð. 14:39:01
ÐÐÐÑ: Artem Polyakov
ÐÐÐÐÑ: gcc-bugs@gcc.gnu.org
ÐÐÐÐ: Re: Broken connect syscall invocation ?
On 26/05/16 07:37 +0000, Artem Polyakov wrote:
>Hello,
>
>I'm using the following version of GCC:
>artpol@artpol-ThinkPad-T430 ~ $ gcc --version
>gcc (Ubuntu 4.8.4-2ubuntu1~14.04.1) 4.8.4
>Copyright (C) 2013 Free Software Foundation, Inc.
>This is free software; see the source for copying conditions. There is NO
>warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
>I'm facing the problem with the slurm compilation:
>https://github.com/SchedMD/slurm
>I'm building the master branch. And the problem I get is related to the following construction:
>https://github.com/SchedMD/slurm/blob/master/src/slurmd/slurmd/req.c#L6171:L6172
>
>The problem I see is that "connect" returns "+1" instead of "-1". And I can't reproduce this with the standalone code:
>https://github.com/artpol84/poc/blob/master/linux-internals/syscalls/connect/cli_c1.c#L37
Hi, this mailing list is used for automated email from our Bugzilla
database and not for reporting bugs.
If you think you've found a bug in GCC please report it using
Bugzilla, rather than mailing this list directly.
https://gcc.gnu.org/bugs/
For general help and support questions about GCC please use the
gcc-help mailing list.
https://gcc.gnu.org/lists.html