Brad House
Brad House
I'm not sure I understand why you'd compile C code with a C++ compiler, can you provide the reason why this is desirable? Is this some limitation of some embedded...
Looking at it `-Wassign-enum` only talks about integer constants, so if we define a `NONE` value of 0 for the flags, the issue would go away, it doesn't look like...
Just tested it, it does warn when you combine 2 enum values as flags: ``` [74/92] Building C object src/lib/CMakeFiles/c-ares.dir/ares_strsplit.c.o /Users/bhouse/svn/c-ares/src/lib/ares_strsplit.c:97:34: warning: integer constant not in range of enumerated type...
Can this warning flag be excluded, or at least be excluded from -Werror in your project? That's a non-standard flag.
A couple of questions, are you only testing windows, or are you also testing linux and linux is fine? Next, if you can try the current 'main', that would be...
have you been able to reproduce this yourself, or only from user reports?
I think maybe there is still an issue as I just saw a test failure on something else I'm working on for Windows x86 with MSVC in a Cancel code...
Also, what compiler is being used when you see the crashes?
initial look at debugging this crash I observed appears to be an issue in the test system itself, so don't think this is related to your crash. I'll know once...
c-ares 1.32.0 is out with the aforementioned fixes. hopefully this version proves stable with EventThread on Windows for you.