[pacman-dev] segfault after curl_easy_cleanup via progress callback
d at falconindy.com
Wed Aug 10 18:48:23 EDT 2011
I received a bug report with backtrace  for a curl powered app that I
work on. It shows a segfault in a progress callback, which is triggered
_after_ curl_easy_cleanup has been called. Unfortunately, I can't
reproduce this, and it's still a development version of pacman with a
limited userbase. There's a half dozen devs using this on a daily basis,
and this is a routine operation that one of us would have surely run
into by now.
That said, the bug reporter was able to find another bug report with
a very similar backtrace. Note that this bug report uses an earlier
version of curl, I believe 7.20, while we're using 7.21.7.
The documentation for curl_easy_cleanup states that further calls to the
handle are invalid after this call so I'm a bit confused as to why curl
would be hitting the progress callback at this point. This indirectly
_insists_ that the application touches the handle. Am I misunderstanding
the expectation of curl_easy_cleanup that it's _possible_ due to an
unfinished transfer that the progress callback may be hit one final
In case it's relevant, I'll point to the where the majority of our curl
implementation lies , but I'm somewhat confident that pacman "does
the right thing" here.
If anyone can point me in the right direction, I've be hugely
More information about the pacman-dev