Begin forwarded message:
Date: Wed, 9 Sep 2015 13:57:38 +0000 From: "bugzilla-dae...@bugzilla.kernel.org" <bugzilla-dae...@bugzilla.kernel.org> To: "shemmin...@linux-foundation.org" <shemmin...@linux-foundation.org> Subject: [Bug 104301] New: Connect failure on sctp socket under debug https://bugzilla.kernel.org/show_bug.cgi?id=104301 Bug ID: 104301 Summary: Connect failure on sctp socket under debug Product: Networking Version: 2.5 Kernel Version: 3.13.0-63-generic Hardware: All OS: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Other Assignee: shemmin...@linux-foundation.org Reporter: riccardomanf...@gmail.com Regression: No When starting an sctp client with gdb, I experience a connect failure (-1 is returned), with errno 106 (Transport endpoint is already connected). If I then cat /proc/net/sctp/assocs, I see the connection and I see the successful handshake on wireshark. If I ignore the connect failure, and pretend I'm actually connected, I can send and receive packets without any trouble. The same client application, run not-under-gdb, does not exhibits the issue and the connect returns 0. -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
