1*1c60b9acSAndroid Build Coastguard Worker** What version of lws ** 2*1c60b9acSAndroid Build Coastguard Worker 3*1c60b9acSAndroid Build Coastguard Worker"vx.y.z" or "01234567 from `main` thismorning" etc 4*1c60b9acSAndroid Build Coastguard Worker 5*1c60b9acSAndroid Build Coastguard WorkerIf it's much older than last stable release, we will likely suggest you try that 6*1c60b9acSAndroid Build Coastguard Workeror `main`. 7*1c60b9acSAndroid Build Coastguard Worker 8*1c60b9acSAndroid Build Coastguard Worker** What platform and arch? ** 9*1c60b9acSAndroid Build Coastguard Worker 10*1c60b9acSAndroid Build Coastguard Worker"Fedora 32 x86_64" or "OSX Catalina" etc 11*1c60b9acSAndroid Build Coastguard Worker 12*1c60b9acSAndroid Build Coastguard Worker** What parts of lws does it involve? ** 13*1c60b9acSAndroid Build Coastguard Worker 14*1c60b9acSAndroid Build Coastguard Workerdunno / core / client / server 15*1c60b9acSAndroid Build Coastguard Workerraw / http / ws / mqtt / other (give me a hint) 16*1c60b9acSAndroid Build Coastguard Worker 17*1c60b9acSAndroid Build Coastguard Worker** How can I reproduce the problem just using lws code? ** 18*1c60b9acSAndroid Build Coastguard Worker 19*1c60b9acSAndroid Build Coastguard WorkerWe can't guess your problem especially in your code. It's great if you can give us a way to 20*1c60b9acSAndroid Build Coastguard Workerrealize our own failure clearly with a reproducer that uses our own code. 21*1c60b9acSAndroid Build Coastguard Worker 22*1c60b9acSAndroid Build Coastguard WorkerTry to remove your code from the equation by trying the same flow on an lws minimal example and provide a little diff against that. We can find out if it's only on your platform, or only on that version, or only in your code from that quickly, and if something to fix in lws, I can confirm it really is fixed using the same test. 23*1c60b9acSAndroid Build Coastguard Worker 24*1c60b9acSAndroid Build Coastguard Worker** Describe the bug ** 25*1c60b9acSAndroid Build Coastguard Worker 26*1c60b9acSAndroid Build Coastguard Worker "fails" --> this word is a red flag you didn't try to debug the issue much... exactly how does it "fail", what evidence is it leaving like logs or return codes or traces? 27*1c60b9acSAndroid Build Coastguard Worker "hangs" --> this word is a red flag you didn't try to debug the issue much... exactly what does it mean, whole device frozen? Spinning 100% cpu? Just idle? Building on fire? Have you tried it via strace or similar if it seems frozen to see what it's doing? Attach a debugger like gdb -p pid and get a backtrace? perf top if Linux to see what it spends its time on. 28*1c60b9acSAndroid Build Coastguard Worker "crashes" --> what happens if you run under valgrind? You know lws is not threadsafe except for lws_cancel_service(), right... 29*1c60b9acSAndroid Build Coastguard Worker "sucks" --> let's discuss you writing a patch to improve whatever it is 30*1c60b9acSAndroid Build Coastguard Worker 31*1c60b9acSAndroid Build Coastguard Worker** Additional data ** 32*1c60b9acSAndroid Build Coastguard Worker 33*1c60b9acSAndroid Build Coastguard WorkerBuild problems? Describe the toolchain and paste the warnings / errors. 34*1c60b9acSAndroid Build Coastguard Worker 35*1c60b9acSAndroid Build Coastguard WorkerCrash? Get a usable backtrace by building with `cmake .. -DCMAKE_BUILD_TYPE=DEBUG` and run under gdb, lldb, or valgrind. 36*1c60b9acSAndroid Build Coastguard Worker 37*1c60b9acSAndroid Build Coastguard WorkerMysterious happenings? Get verbose lws logs by building with `cmake .. -DCMAKE_BUILD_TYPE=DEBUG` and run with `lws_set_log_level(1151, NULL)`, on the example apps they all take a switch like -d1151. 38*1c60b9acSAndroid Build Coastguard Worker 39