Re: crash seen in multi_socket

On Sun, 12 May 2019, Kunal Ekawde wrote:

> Ok, I shall try to update to 7.64.1 but that would take sometime to
> integrate, sanitize and load run.

Note: I don't think upgrading will fix this particular issue.

> but using this patch resulted in trap #2. Based on trap #2 backtrace,

I didn't understand that backtrace. Any chance you can rebuild your libcurl
and keep the debug symbols so that we can see exactly from what source lines
the functions are called? Maybe even stop there with gdb and do 'bt full'!

Why exactly is it crashing there? Is that a NULL pointer dereference or
something?

> I've update the patch to 'return result;' //CURLM_OK instead of continue. I
> m yet to verify the minimal load run with the server abruptly terminating
> case, which most likely resulted in trap #2. Do you think 'result result;'
> is not correct there ?

It is not correct. We need the rest of the logic in the function to run.

> One thing missing there would be updating running_handles.

For example, yes, but we also need to take care of the timers that might have
expired.

-- 
  / daniel.haxx.se | Get the best commercial curl support there is - from me
                   | Private help, bug fixes, support, ports, new features
                   | https://www.wolfssl.com/contact/
-------------------------------------------------------------------
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html