akallabeth

@kstest1 great. I´ve only got dual monitor setups to test, but maybe that is enough. A quick way to test is to just install in `/tmp/freerdp` or similar instead of...

@jtaylor87 currently only manual fingerprint verification is implemented, assuming you're using xfreerdp.

@colemickens ok, any details? the 2 tests run on our ci for years now, so maybe you have something unique or differing from our setup that triggers that?

@colemickens ok, which environment and compile options do you use (including cmake options)? aside from that, you might want to check https://stackoverflow.com/questions/5709914/using-cmake-how-do-i-get-verbose-output-from-ctest#5757256

@colemickens you add `-DBUILD_TESTING=ON` to release builds? a very bad idea, the tests change the ABI so that they can access freerdp internal functions. also: * `-DWITH_SSE2=ON` is not required,...

@ernsteiswuerfel best run the test manually with `./Testing/TestSynch TestSynchCritical` in your build dir, then you might get some output. (or run it in a debugger as it tells `segfault` )...

> This way the only output I get is: > > ``` > ~/builddir/FreeRDP/build # ./Testing/TestSynch TestSynchCritical > Deadlock will be assumed after 400 ms. > ``` > > Nothing...

interesting datapoint. so this crashes somewhere after the test completed in some cleanup code of openssl or libc?

@ernsteiswuerfel ok, looks like there is something very wrong here: `CriticalSection failure: Possible dead lock detected` (did miss that yesterday in all this text 😁 ) looks like the `CriticalSection`...

@luizluca sorry for the delay, but could you check where in `wlf_cliprdr_server_format_data_request` the request fails?