I recently upgraded distro-packaged (openSUSE) curl/libcurl from v7.66 -> 7.67.
Subsequently, when I exec the distro's package management tool (zypper), it
works for accessing ALL defined repos without problem/error, except for one, at
which it reproducibly SEGFAULTs (~60+ machines, so far).
Do
>> *Is* this^^ likely a curl issue?
>
>
> There's not enough information to tell. I downloaded that appdata file
> without a problem using 7.67 but I'm using Windows. We need a link to
> the issue filed with the repo and a minimal self-contained example that
> can be used to reproduce. Find out i
On 11/12/19 11:12 AM, PGNet Dev wrote:
> >> *Is* this^^ likely a curl issue?
> >
> >
> > There's not enough information to tell. I downloaded that appdata file
> > without a problem using 7.67 but I'm using Windows. We need a link to
> > the issue filed with the repo and a minimal self-conta
> might help. I'll take a look with that enabled here in a bit.
With that increased verbosity ...
ZYPP_MEDIA_CURL_DEBUG=2 zypper ref OS15-oss
journalctl -f
Nov 13 13:36:49 vm013 kernel: traps: zypper[3470] general protection
fault ip:7fdd10cec910 sp:7ffc76592bf0 error:0 in
libcurl.s
On 11/13/19 2:39 PM, Daniel Stenberg wrote:
> If this crash is at least semi-reliably reproduced in your environment
100%, on all machines tested so far.
Unfortunately, I've not yet found any OTHER reports from others'
> then maybe you can try building a libcurl from source with the debug symbol
On 11/13/19 4:03 PM, PGNet Dev wrote:
> On 11/13/19 2:39 PM, Daniel Stenberg wrote:
>> If this crash is at least semi-reliably reproduced in your environment
>
> 100%, on all machines tested so far.
>
> Unfortunately, I've not yet found any OTHER reports from others'
>
>> then maybe you can try
> note,
>
>curl_multi_add_handle() @
>
> https://github.com/openSUSE/libzypp/blob/02a52477c0378127d0c13e4797826ee1367936ac/zypp/media/MediaMultiCurl.cc#L763
>
and,
#0 Curl_splay (i=..., t=0x563d07704238) at splay.c:55
https://github.com/curl/curl/blob/2e9b725f67d49a9d7a1f053f
On 11/13/19 10:26 PM, Daniel Stenberg wrote:
> We fixed a bug the other day that could possibly be related:
>
>
> https://github.com/curl/curl/commit/13182b33f727cf5a56a5a13419904369f7f3baad
I patched that into a v7.67 build, and tested.
Looks like it solves the problem,
https://bugzilla
On 3/22/20 8:23 AM, Rohith Jayakumar via curl-library wrote:
> Hi,
> I would like to know if there is any latest curl version that supports
> openssl1.1.1.
> I am trying to build the curl version 7_69_1 linking it with openssl1.1.1,
> but I am facing few reference errors with the api's which are
On 3/23/20 12:13 AM, Rohith Jayakumar wrote:
> After removing the old include path from the CPP flags, things worked fine...
for an env with multiple openssl installs, sanity-check your curl bins' *run*
time lib paths as well.
making sure build/link-time rpath-ing is used/correct helps avoid
On 4/13/20 1:52 PM, Jeffrey Walton via curl-library wrote:
>> Now I was wondering is it even possible to use this cipher anymore or am I
>> just missing something?
3DES suites are disabled by default since 1.1.0 release in ~2016
cat openssl-1.1.1f/CHANGES
...
11 matches
Mail list logo
