Re: [Chicken-hackers] [PATCH] Ensure va_end() is always called in C_a_i

chicken-hackers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-hackers] [PATCH] Ensure va_end() is always called in C_a_i_

From:	Evan Hanson
Subject:	Re: [Chicken-hackers] [PATCH] Ensure va_end() is always called in C_a_i_string()
Date:	Sun, 22 Jan 2017 11:43:27 +1300

On 2017-01-20 16:28, Kooda wrote:
> Looks fine, pushed!

Thanks Kooda!

> I’m curious though: how did you catch this?

http://cppcheck.sourceforge.net/

Evan

[Prev in Thread]

Current Thread

[Next in Thread]

[Chicken-hackers] [PATCH] Ensure va_end() is always called in C_a_i_string(), Evan Hanson, 2017/01/19
- Re: [Chicken-hackers] [PATCH] Ensure va_end() is always called in C_a_i_string(), Kooda, 2017/01/20
  - Re: [Chicken-hackers] [PATCH] Ensure va_end() is always called in C_a_i_string(), Evan Hanson <=

Prev by Date: Re: [Chicken-hackers] [PATCH 0/1] Fix spurious array bounds warnings on OpenBSD
Next by Date: Re: [Chicken-hackers] [PATCH 0/1] Fix spurious array bounds warnings on OpenBSD
Previous by thread: Re: [Chicken-hackers] [PATCH] Ensure va_end() is always called in C_a_i_string()
Next by thread: [Chicken-hackers] [PATCH 0/1] Fix spurious array bounds warnings on OpenBSD
Index(es):
- Date
- Thread