Closed fishjam closed 2 years ago
After fix it:
E:\CodeGithub\fishjam-Detours\bin.X64>syelogd.exe
SYELOGD: Ready for clients. Press Ctrl-C to stop.
20220614052404152 14272 50.60: fishjam test thread:1, testIndex:0
20220614052404152 14272 50.60: fishjam test thread:1, testIndex:1
20220614052404153 14272 50.60: fishjam test thread:1, testIndex:2
20220614052404155 14272 50.60: fishjam test thread:2, testIndex:0
20220614052404155 14272 50.60: fishjam test thread:1, testIndex:3
20220614052404155 14272 50.60: fishjam test thread:2, testIndex:1
20220614052404155 14272 50.60: fishjam test thread:1, testIndex:4
20220614052404155 14272 50.60: fishjam test thread:2, testIndex:2
20220614052404155 14272 50.60: fishjam test thread:1, testIndex:5
20220614052404156 14272 50.60: fishjam test thread:2, testIndex:3
20220614052404157 14272 50.60: fishjam test thread:3, testIndex:0
20220614052404156 14272 50.60: fishjam test thread:1, testIndex:6
20220614052404157 14272 50.60: fishjam test thread:2, testIndex:4
...
Describe the bug I have written a UT code with multi thread client to test my pipe server(include the syelog), and I found if there are lots of client request connect to syelog at same time, there is ERROR_PIPE_CONNECTED when call ConnectNamedPipe , ad no err handle for it.
Command-line test case
Expected behavior I fix it by add the speical error handle, and will create the PR for it.
Detours version