Summary: | dev-vcs/git[curl] segfault in git-remote-https after typo in clone command | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | lekto |
Component: | Current packages | Assignee: | Robin Johnson <robbat2> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | lekto, polynomial-c |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://marc.info/?l=git&m=147325585811281&w=2 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | emerge --info |
Description
lekto
2016-08-31 06:11:09 UTC
Created attachment 444526 [details]
emerge --info
Any chance you can report that to upstream as well? It might be a Gentoo bug, git-9999 gives me a segfault too. When I manually download, compile and install git I get message "<url> malformed". Should I report this to upstream anyway? (In reply to lekto from comment #4) > Should I report this to upstream anyway? No. Let's find the cause for this issue first. Strcmp (glib-2.23-r2) in http.c:606 is causing this segfault.
After remove this whole block (605-616) git don't cause segfault anymore, but I probably broke something else.
http.c:605
>if (!curl_http_proxy) {
> if (!strcmp(http_auth.protocol, "https")) {
> var_override(&curl_http_proxy, getenv("HTTPS_PROXY"));
> var_override(&curl_http_proxy, getenv("https_proxy"));
> } else {
> var_override(&curl_http_proxy, getenv("http_proxy"));
> }
> if (!curl_http_proxy) {
> var_override(&curl_http_proxy, getenv("ALL_PROXY"));
> var_override(&curl_http_proxy, getenv("all_proxy"));
> }
>}
Bug has been reported upstream and a fix was provided that will hopefully be in the next release of git. Fixed in git-2.10.1 |