After few weeks without much testing on that terms from me, have a question: will it ok if i will make a BZ for bsdsocket just with what i have there ? I can just attach info about how to build libcurl, ready to test libcurl.a from it, and also that test case which hangs after few tries of sending blocked connections. At least if it will be fixed, then i can re-port muiowb with enabled threaded curl resolver => no more blocking.I really wish a bug report was filed...
Nothing has been done and this will likely continue until at least a bug report is filed against bsdsocket.library.
Threaded libcurl crash
Re: Threaded libcurl crash
@steven
Re: Threaded libcurl crash
You may also send a proper report via mail to the author of bsdsocket, it might be the faster way if the problem is really related to that
Re: Threaded libcurl crash
@samo
you can be sure i know how to find out faster ways
(already contacted with Olaf few times about in last half of year). Bug should be in BZ, so anyone can have a look at and chances are bigger. Just BZ should be done right, with all details and very easy reproducible test cases : thats why i ask if that what we have is enough (because is not and person who will worry will need to dig in a lot in all of this).
you can be sure i know how to find out faster ways
(already contacted with Olaf few times about in last half of year). Bug should be in BZ, so anyone can have a look at and chances are bigger. Just BZ should be done right, with all details and very easy reproducible test cases : thats why i ask if that what we have is enough (because is not and person who will worry will need to dig in a lot in all of this).
Re: Threaded libcurl crash
Yes, I think there is enough information to file a bug report against bsdsocket.library. The simpler it is to recreate the problem the better of course.kas1e wrote:After few weeks without much testing on that terms from me, have a question: will it ok if i will make a BZ for bsdsocket just with what i have there ? I can just attach info about how to build libcurl, ready to test libcurl.a from it, and also that test case which hangs after few tries of sending blocked connections. At least if it will be fixed, then i can re-port muiowb with enabled threaded curl resolver => no more blocking.
ExecSG Team Lead
Re: Threaded libcurl crash
@Steven
Done. BZ #8340. I tryed to do report as much simple as possible with much as possible details, logs, examples, and stuff. that include test case, sources+library of latest libcurl which i build today, and all possible information.
Its even now have even more info in compare with previous reports: as i use now latetest debug kernel with MUNGE option, it bring DEADBEEF to register (so memory was freed already), which somehow can point out on something. Check it plz.
Done. BZ #8340. I tryed to do report as much simple as possible with much as possible details, logs, examples, and stuff. that include test case, sources+library of latest libcurl which i build today, and all possible information.
Its even now have even more info in compare with previous reports: as i use now latetest debug kernel with MUNGE option, it bring DEADBEEF to register (so memory was freed already), which somehow can point out on something. Check it plz.