On Thu, 3 Feb 2022, Lilia Boneva via curl-library wrote:
Today I installed new 7.81 version (hoping for fixed issue) , but the system
went into infinite loop at same place after 4 hours.
Is there a way to minimise the possiblility of infinite loop ?
First, I would be very careful with drawi
Hello team,
Is anyone building or using a modern (lib)curl on TPF?
Back in September 2010 we did the last "confirmed working" change to curl that
builds on TPF (commit 7e1a45e224e57).
I did find the book "z/TPF Application Modernization using Standard and Open
Middleware" [1], published in 2
> Am 03.02.2022 um 10:55 schrieb Daniel Stenberg via curl-library
> :
>
> Hello team,
>
> Is anyone building or using a modern (lib)curl on TPF?
>
> Back in September 2010 we did the last "confirmed working" change to curl
> that builds on TPF (commit 7e1a45e224e57).
>
> I did find the boo
On Thu, Feb 3, 2022 at 6:56 AM Daniel Stenberg via curl-library
wrote:
>
> Hello team,
>
> Is anyone building or using a modern (lib)curl on TPF?
>
> Back in September 2010 we did the last "confirmed working" change to curl that
> builds on TPF (commit 7e1a45e224e57).
>
> I did find the book "z/TP
Hello,
in the past I used the curl for zTPF version to make curl available for
zOS also. As long as the zOS support is still available a backport to
zTPF should be easy.
>> Is anyone building or using a modern (lib)curl on TPF?
>>
>
> You are way too gentle with this proprietary niche OS thingie
On Thu, 3 Feb 2022, Lutz Mader via curl-library wrote:
in the past I used the curl for zTPF version to make curl available for zOS
also. As long as the zOS support is still available a backport to zTPF
should be easy.
curl has been made to run on z/OS in the past [1] but if they then needed t
I've tried to dive a bit deeper on this subject and still not really sure
why google.com despite the redirect triggers so many strlen calls in curl,
fetching https://curl.se/ yields only 173 calls so almost 1/4 the amount
from the google case.
23% of those for curl.se and 8% for google.com is due
On 03-Feb-22 20:09, Henrik Holst via curl-library wrote:
the traces only shows that strlen was called, not on which string it
was called so the digging is a bit time consuming).
Doesn't have to be too painful; automate:
Set on-the-fly breakpoints where strlen is called, and display the
argum
On Thu, Feb 03, 2022 at 08:35:13PM -0500, Timothe Litt via curl-library wrote:
> On 03-Feb-22 20:09, Henrik Holst via curl-library wrote:
>> the traces only shows that strlen was called, not on which string it was
>> called so the digging is a bit time consuming).
> Set on-the-fly breakpoints where
problems is that ltrace produces zero output, if I compile curl with
--no-pie then ltrace produces some output but not a single strlen for some
reason so I gave up on that and found uftrace instead which works but only
shows which functions that are called and not the arguments.
/HH
Den fre 4 feb
On 03-Feb-22 21:02, Henrik Holst via curl-library wrote:
problems is that ltrace produces zero output, if I compile curl with
--no-pie then ltrace produces some output but not a single strlen for
some reason so I gave up on that and found uftrace instead which works
but only shows which functi
did static compile as well. will try out gdb perhaps during the weekend,
but we are still talking about 490 data points here.
Den fre 4 feb. 2022 kl 03:10 skrev Timothe Litt via curl-library <
curl-library@lists.haxx.se>:
>
> On 03-Feb-22 21:02, Henrik Holst via curl-library wrote:
>
> problems i
On Fri, 4 Feb 2022, Henrik Holst wrote:
23% of those for curl.se and 8% for google.com is due to Curl_compareheader,
this looks like an internal only function and every single use inside curl
is using string literals so we can replace them all with a compile time
sizeof, if patches for this wo
13 matches
Mail list logo
