Login at Kodi Home

**wsnipex** · 2014-09-21, 08:18

its just for reference for the curl devs

**fritsch** · 2014-09-21, 08:51

Yes, you are right. Hopefully they follow this thread.

geearf · 2014-09-22, 00:24

(2014-09-21, 07:55)fritsch Wrote: Nice, Johne E has tracked it down: http://sourceforge.net/p/curl/bugs/1426/

From looking at the patch - it seems like the logic in: https://github.com/bagder/curl/commit/ca...18bc82ebfb , especially: https://github.com/bagder/curl/commit/ca...feb02R1572

Can you try to change that like:

Code:
- Curl_expire_latest(data->easy_conn->recv_pipe->head->ptr, 1); + Curl_expire(data->easy_conn->recv_pipe->head->ptr, 1);

I think a curl timesout before actually getting anything.

I tried that but no, it didn't help. :/
(I'm John E on sf)

**fritsch** · 2014-09-22, 08:17

Oki, then let's find out what upstream has to tell. They know their code way better. Thanks for bisecting.

geearf · (This post was last modified: 2014-09-22, 09:27 by geearf.)

Sure, that was my first time doing that, it was interesting for me as well!
Oh and by the way, unlike what you wrote in the previous page, I didn't need to rebuild xbmc, building curl and restarting xbmc was enough.

**fritsch** · (This post was last modified: 2014-09-22, 12:39 by fritsch.)

@geearf: Please enable detailled curl logging like wsnipex said. This log will get much more useful. It's under debug logging, component logging.

geearf · 2014-09-22, 23:15

Is there a way to have debug logging without it affecting the ui?

**fritsch** · 2014-09-23, 08:17

Yes - see: http://wiki.xbmc.org/?title=advancedsettings.xml

geearf · 2014-09-23, 08:46

Got it!
But since I have to "deactive" debugging in the UI, how do I specify the component logging?
Or does '1' gets all of components anyway?

**fritsch** · 2014-09-23, 08:48

You only need to gather logfiles exactly once - so I would just enable gui logging, restart xbmc - scrape something and provide the logfile afterwards. Then you can disable logging again.

**Martijn** · 2014-09-23, 08:48

(2014-09-23, 08:46)geearf Wrote: Got it!
But since I have to "deactive" debugging in the UI, how do I specify the component logging?
Or does '1' gets all of components anyway?

it's a bug.
you can't active component logging with advancedsettings enabled.

perhaps it works if you first enable component logging and then activate advancedsettings

geearf · 2014-09-23, 09:56

(2014-09-23, 08:48)fritsch Wrote: You only need to gather logfiles exactly once - so I would just enable gui logging, restart xbmc - scrape something and provide the logfile afterwards. Then you can disable logging again.

Well I understand that, it was more of a general question than a how-to-debug-right-now.

(2014-09-23, 08:48)Martijn Wrote:
(2014-09-23, 08:46)geearf Wrote: Got it!
But since I have to "deactive" debugging in the UI, how do I specify the component logging?
Or does '1' gets all of components anyway?

it's a bug.
you can't active component logging with advancedsettings enabled.

perhaps it works if you first enable component logging and then activate advancedsettings

That's unfortunate.

Thanks!

**fritsch** · 2014-09-23, 11:51

Arch Users: http://sourceforge.net/p/curl/bugs/1426/ <- please test and give Daniel a big thank you and the data he wants.

Thanks much in advance from my side.

graysky · 2014-09-23, 22:25

Thank you to all the folks in there (especially you, fritsch) who helped Daniel trouble shoot and fix this. The patch works great.

**fritsch** · (This post was last modified: 2014-09-23, 22:26 by fritsch.)

Daniel did the work completely. I only linked him our commonoptions. Please also thank especially him in the libcurl bugtracker. He invested a whole lot of time to debug that issue. He even wrote custom code to reproduce it. This is outstanding!