Summary: | Mono 4.4.0 crashes when using Socket.ConnectAsync to a unix domain socket if the path doesn't exist | ||
---|---|---|---|
Product: | [Mono] Class Libraries | Reporter: | kirankulkarni747 |
Component: | System | Assignee: | marcos.henrich |
Status: | VERIFIED FIXED | ||
Severity: | normal | CC: | jahmai, jkolb, luis.aguilera, masafa, mohitk, mono-bugs+mono, mono-bugs+runtime, peter.collins |
Priority: | --- | ||
Version: | 4.4.0 (C7) | ||
Target Milestone: | (C7SR1) | ||
Hardware: | Macintosh | ||
OS: | Mac OS | ||
Tags: | Is this bug a regression?: | Yes | |
Last known good build: | 4.2.3 |
Description
kirankulkarni747
2016-06-08 18:42:45 UTC
Hi Kiran, Thanks for the bug report, This should be fixed by PR 3210 https://github.com/mono/mono/pull/3210. Once this is reviewed and merged I will do a cherry pick and pull request into the next service release. I'm seeing this on Xamarin Android latest stable. Hi jkolb, thanks for letting us know. Fixed in master 80d015b2df275ad48fa77c02224f6ebc7e08bbd4 https://github.com/mono/mono/commit/80d015b2df275ad48fa77c02224f6ebc7e08bbd4 Fixed in mono-4.5.1-branch 0935e38357fa71312c701ed6aeec5459dec84a95 https://github.com/mono/mono/commit/0935e38357fa71312c701ed6aeec5459dec84a95 Open a request for adding the fix on the next service release: https://github.com/mono/mono/pull/3237 Trello card: https://trello.com/c/nq8lB7dO/61-mono-41616-mono-4-4-0-crashes-when-using-socket-connectasync looks like this should be in resolved/fixed state after comment 3 This issue has been fixed with http://storage.bos.xamarin.com/mono-master/b0/b07703ed573597c2e2881d15f2b46488570a981a/MonoFramework-MDK-4.5.2.474.macos10.xamarin.universal.pkg Screencast : http://www.screencast.com/t/MBuZEhb1 Thanks Fixed in mono-4.4.0-branch 5b18268ddbadb2033c457e224f9ce12bae623809 https://github.com/mono/mono/commit/5b18268ddbadb2033c457e224f9ce12bae623809 I'm seeing something similar in that when ConnectAsync encounters an error and returns false, it still fires the callback asynchronously. Does this fix address this scenario or should I raise another bug? @Jahmai, please open a new bug report with a test case for your issue and let me know of it. |