Team A
[ZBX-15094] Possible crash during vmware update Created: 2018 Oct 30 Updated: 2024 Apr 10 Resolved: 2018 Oct 31 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 4.0.1, 4.2.0alpha1 |
| Fix Version/s: | 4.0.2rc1, 4.2.0alpha1, 4.2 (plan) |
| Type: | Problem report | Priority: | Minor |
| Reporter: | Andris Zeila | Assignee: | Michael Veksler |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Team: | Team A |
| Sprint: | Sprint 46, Nov 2018 |
| Story Points: | 0.5 |
| Description |
________________________________________________________________________________________________________ *** CID 184230: Memory - illegal accesses (UNINIT) /src/zabbix_server/vmware/vmware.c: 3845 in vmware_service_update() 3839 goto clean; 3840 3841 ret = SUCCEED; 3842 clean: 3843 curl_slist_free_all(headers); 3844 curl_easy_cleanup(easyhandle); >>> CID 184230: Memory - illegal accesses (UNINIT) >>> Using uninitialized value "page.data". 3845 zbx_free(page.data); 3846 3847 zbx_vector_str_clear_ext(&hvs, zbx_str_free); 3848 zbx_vector_str_destroy(&hvs); 3849 out: 3850 zbx_vmware_lock(); This happens when setting headers fails. From libcurl documentation curl_easy_setopt with CURLOPT_HTTPHEADER:
I understand that requires specific libcurl build without HTTP support. So the priority is minor, still has to be fixed. |
| Comments |
| Comment by Michael Veksler [ 2018 Oct 31 ] |
|
Available in:
|