On Sun, 17 Mar 2019, Casper wrote:
The additional updates appear to have solved the issues - no crashing now.
This is great! Fingers crossed that it stays that way. (Not interesting any
more - but it was the example unmodified on Linux (Ubuntu 16.04.5), gcc
5.4.0)
Cool, thanks for verifying.
The additional updates appear to have solved the issues - no crashing now. This
is great! Fingers crossed that it stays that way.
(Not interesting any more - but it was the example unmodified on Linux (Ubuntu
16.04.5), gcc 5.4.0)
C.
‐‐‐ Original Message ‐‐‐
On Sunday, March 17, 2019 9:0
On Sun, 17 Mar 2019, Casper wrote:
Unfortunately the fix did not work for me. I built your branch and tried
with the lib and saw the following:
I didn't get exactly that crash myself but further experimenting with the
example code in my branch (and a scan-build) revealed some remaining proble
Unfortunately the fix did not work for me. I built your branch and tried with
the lib and saw the following:
Core was generated by `./threaded-shared-conn'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00420e94 in pausewrite ()
[Current thread is 1 (Thread 0x7f95d1ffb
That's great! I will send an update if I find any further problems. Thanks
again!
‐‐‐ Original Message ‐‐‐
> The code freeze is for "features", we will keep merging bug-fixes until just a
> day or two before the pending release. So I hope that this fix will ship in
> 7.64.1!
>
>
On Sun, 17 Mar 2019, Casper wrote:
Thanks for your quick response! I will give it a go, while it works through
reviews and gets into the master.
I believe the 7.64.1 code freeze was last Wednesday? Is your expectation
that this will be included in the release after? I assume that's 2 months
Thanks for your quick response! I will give it a go, while it works through
reviews and gets into the master.
I believe the 7.64.1 code freeze was last Wednesday? Is your expectation that
this will be included in the release after? I assume that's 2 months from now,
looking at your past release
On Sat, 16 Mar 2019, Daniel Stenberg via curl-library wrote:
I can reproduce and I'm on it. I believe this regression was introduced
between 7.61.0 and 7.62.0.
Here's my first take a fix: https://github.com/curl/curl/pull/3686
--
/ daniel.haxx.se
On Fri, 15 Mar 2019, Casper via curl-library wrote:
The executable I build from the sample, threaded-shared-conn.c crashes
pretty much every single time. It is linked to libcurl 7.64.0 static
library. This is on Linux (Ubuntu 16.04.5), gcc 5.4.0. Here is an example
backtrace:
I can reproduce
Hello
The executable I build from the sample, threaded-shared-conn.c crashes pretty
much every single time. It is linked to libcurl 7.64.0 static library. This is
on Linux (Ubuntu 16.04.5), gcc 5.4.0. Here is an example backtrace:
Core was generated by `./threaded-shared-conn'.
Program
10 matches
Mail list logo
