arestest segfaults for me

2016-09-23 Thread Daniel Stenberg
Hey, As I'm currently fiddling with some c-ares functions I figured I should get the tests running properly to allow me to verify my pending changes. I built c-ares with the tests enabled, only to figure out that 'make test' ends up in a segfault with the current git master! If I manually s

Re: arestest segfaults for me

2016-09-23 Thread David Drysdale via c-ares
On Fri, Sep 23, 2016 at 8:25 AM, Daniel Stenberg wrote: > Hey, > > As I'm currently fiddling with some c-ares functions I figured I should > get the tests running properly to allow me to verify my pending changes. > > I built c-ares with the tests enabled, only to figure out that 'make test' > en

Re: arestest segfaults for me

2016-09-23 Thread Daniel Stenberg
On Fri, 23 Sep 2016, David Drysdale wrote: Is that just with valgrind, or are there problems with a normal run too? Ah sorry for being unclear: no it crashes in normal runs as well which is why I decided to try valgrind on it to see what it says. When I run 'make test' the end of my test-su

Re: arestest segfaults for me

2016-09-23 Thread David Drysdale via c-ares
I can't reproduce the problem, so could you try doing a non-valgrind debug build and seeing what pops out in the debugger (e.g. libtool --mode=execute gdb ./arestest)? The stack makes it look like a null pointer is being passed down, only it's for a C++ reference rather than a pointer so that seem

Release coming up!

2016-09-23 Thread Daniel Stenberg
Hello! I think it is about time to bring the band back together and do another c-ares release! I don't have a date just yet, this is just a wake-up call. So, if you have stuff to merge before we ship anything please bring it back up on the table and let's see what we can do. There are still

Re: Release coming up!

2016-09-23 Thread David Drysdale via c-ares
On Fri, Sep 23, 2016 at 2:44 PM, Daniel Stenberg wrote: > Hello! > > I think it is about time to bring the band back together and do another > c-ares release! I don't have a date just yet, this is just a wake-up call. > > So, if you have stuff to merge before we ship anything please bring it > ba

Re: Release coming up!

2016-09-23 Thread Brad House via c-ares
I'd like to re-open the discussion of the last patch I sent via this mailing list: "[PATCH] remove configure-time type size checks" This fixes multi-arch building for iOS and MacOSX (without requiring separate builds and using lipo to join them), and has been tested across a large number of platf

Re: Release coming up!

2016-09-23 Thread Daniel Stenberg
On Fri, 23 Sep 2016, Brad House via c-ares wrote: I'd like to re-open the discussion of the last patch I sent via this mailing list: "[PATCH] remove configure-time type size checks" This fixes multi-arch building for iOS and MacOSX (without requiring separate builds and using lipo to join the

Re: Release coming up!

2016-09-23 Thread Brad House via c-ares
On 09/23/2016 05:35 PM, Daniel Stenberg wrote: > On Fri, 23 Sep 2016, Brad House via c-ares wrote: > >> I'd like to re-open the discussion of the last patch I sent via this mailing >> list: "[PATCH] remove configure-time type size checks" >> >> This fixes multi-arch building for iOS and MacOSX (wi