[pgpool-general: 1956] memory overrun bug?

Sean Hogan sean at compusult.net
Tue Jul 30 21:08:04 JST 2013


I noticed what appears to be a bug in watchdog/wd_interlock.c.  In 
wd_init_interlock, a shared memory segment of size 8 is created 
(assuming a 64-bit machine).  Then a few lines later memset is called, 
clearing 40 bytes starting at that shared memory location. Shouldn't the 
allocation and memset both use "sizeof(bool) * WD_MAX_LOCK_NUM"?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: sean.vcf
Type: text/x-vcard
Size: 275 bytes
Desc: not available
URL: <http://www.sraoss.jp/pipermail/pgpool-general/attachments/20130730/dcfe0f1a/attachment.vcf>

More information about the pgpool-general mailing list