- Oct 13, 2008
- Oct 12, 2008
-
-
Yang Tse authored
-
Yang Tse authored
Highest warning level is double -A, next is single -A. Due to the big number of warnings these trigger on third party header files it is impratical for us to use any of them here. If you want them simply define it in CPPFLAGS.
-
Dan Fandrich authored
-
Dan Fandrich authored
use the startup of the IPv6 test server as a substitute check for this).
-
- Oct 11, 2008
- Oct 10, 2008
-
-
Dan Fandrich authored
-
Yang Tse authored
-
Patrick Monnerat authored
_ Update RPG binding accordingly. _ Fix new options comments.
-
Yang Tse authored
-
Yang Tse authored
-
Yang Tse authored
2) Disable SGI remark: controlling expression is constant
-
Yang Tse authored
-
Dan Fandrich authored
-
Yang Tse authored
-
Yang Tse authored
Due to the HP-UX socklen_t issue it is insane to use the +w1 warning level. It generates more than 1100 warnings on socklen_t related statements. Until the issue is somehow fixed we will just use the +w2 warning level.
-
Yang Tse authored
-
Yang Tse authored
-
- Oct 09, 2008
-
-
Dan Fandrich authored
-
Daniel Stenberg authored
because the struct is declared on the stack and not all members are used so we could just as well make struct with only struct members we actually need.
-
Dan Fandrich authored
for spotting it).
-
Yang Tse authored
-
Dan Fandrich authored
systems supporting getifaddrs(). Also fixed a problem where an IPv6 address could be chosen instead of an IPv4 one for --interface when it involved a name lookup.
-
Dan Fandrich authored
-
Dan Fandrich authored
-
Yang Tse authored
-
Yang Tse authored
-
Dan Fandrich authored
All but the first test cause an infinite loop or other failure and so are added to DISABLED.
-
Yang Tse authored
-
Yang Tse authored
-
Yang Tse authored
Disallow run-time dereferencing of null pointers. Disable some remarks: #4227: padding struct with n bytes to align member. #4255: padding size of struct with n bytes to alignment boundary.
-
Yang Tse authored
-
- Oct 08, 2008
-
-
http://curl.haxx.se/bug/view.cgi?id=2152270Daniel Stenberg authored
fixed a CURLINFO_REDIRECT_URL memory leak and an additional wrong-doing: Any subsequent transfer with a redirect leaks memory, eventually crashing the process potentially. Any subsequent transfer WITHOUT a redirect causes the most recent redirect that DID occur on some previous transfer to still be reported.
-
Dan Fandrich authored
-