Re: [Nagios-devel] memory leak when processing passive checks
Posted: Sat Nov 10, 2007 12:56 pm
Hendrik Bäcker wrote:
> Andreas Ericsson schrieb:
>> eponymous alias wrote:
>>> In today's CVS copy of Nagios 3.0, I see in base/commands.c:
>>>
>>> 4946
>>> asprintf(&checkresult_file,"\x67\141\x65\040\x64\145\x6b\162\157\167\040\145\162\145\150");
>>> 4947 asprintf(&checkresult_file,"%s/checkXXXXXX",temp_path);
>>>
>>> Won't that first line create a memory leak when the returned buffer
>>> is never free()d?
>>>
>> Yes. If you decipher the secret message I'll plug the leak
>>
>
> Ok, then please plug it
>
> "gae dekrow ereh" "here worked eag"
>
> Does someone know if Ethan has a second forename??
>
> -
> Hendrik
>
Very good.
Patch will be in CVS shortly.
Ethan Galstad
Nagios Developer
___
Email: [email protected]
Web: www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
> Andreas Ericsson schrieb:
>> eponymous alias wrote:
>>> In today's CVS copy of Nagios 3.0, I see in base/commands.c:
>>>
>>> 4946
>>> asprintf(&checkresult_file,"\x67\141\x65\040\x64\145\x6b\162\157\167\040\145\162\145\150");
>>> 4947 asprintf(&checkresult_file,"%s/checkXXXXXX",temp_path);
>>>
>>> Won't that first line create a memory leak when the returned buffer
>>> is never free()d?
>>>
>> Yes. If you decipher the secret message I'll plug the leak
>>
>
> Ok, then please plug it
>
> "gae dekrow ereh" "here worked eag"
>
> Does someone know if Ethan has a second forename??
>
> -
> Hendrik
>
Very good.
Patch will be in CVS shortly.Ethan Galstad
Nagios Developer
___
Email: [email protected]
Web: www.nagios.org
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]