[Slackbuilds-users] tangogps slackbuild doesn't work

Donald Allen donaldcallen at gmail.com
Sun Jul 31 23:31:51 UTC 2011

On Sun, Jul 31, 2011 at 5:39 PM, B Watson <yalhcru at gmail.com> wrote:

> On 7/31/11, Donald Allen <donaldcallen at gmail.com> wrote:
> > If you google for 'libcurl "error 6" segfault', you get hits involving
> all
> > sorts of applications that apparently use curl. Try it. This looks to me
> > like a bug in libcurl. So unless you are feeling better, stay in bed.
> This
> > appears to be someone else's problem.
> This sounds really similar to the issue with uget that I dealt with a
> while back.
> If it's the same issue, it can be fixed by adding
> curl_easy_setopt(curl, CURLOPT_NOSIGNAL, 1);
> somewhere in the bit of code that sets the other curl options.
> The issue is actually documented in the curl API docs: if curl is
> built with threads but without c-ares support (like the one shipped
> with slackware), the default DNS timeout handling (which uses signals,
> presumably SIGALRM) is unsafe.
> Adding to the confusion is that (at least in the case of uget) this
> didn't actually hurt anything on slackware 13.1, but it does on 13.37.
> I dunno if you can consider this a bug in curl or not: it's documented,
> but if I were a curl dev, I'd want to fix it (by having CURLOPT_NOSIGNAL
> default to 1 when curl is built without c-ares). Application code can
> set CURLOPT_NOSIGNAL, but I don't know how hard it is for a configure
> script or makefile to detect whether curl was built with c-ares, and I
> don't know what happens if you set CURLOPT_NOSIGNAL when using a libcurl
> with c-ares support.

Thanks for this -- I'll try it. It sounds like the curl people may not have
chosen the most conservative default, but you concede to not completely
understanding the trade-offs and I know a good deal less than you do about
this, so I will leave this as pure speculation.

I will report back to the list when either

1. I've run tangogps for a good deal longer than the
mean-time-between-segfaults without a crash, or
2. I continue to see segfaults even with the suggested fix installed..


> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> http://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - http://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - http://slackbuilds.org/faq/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20110731/01215374/attachment-0001.html>

More information about the SlackBuilds-users mailing list