|02:43 pm - Zen Error Message of the Week|
From last week, I guess I didn't post this. I'm in the midst of hunting some odd memory bugs. valgrind is an excellent tool. But, sometimes...
==22728== 0 bytes in 1 blocks are definitely lost in loss record 1 of 32
==22728== at 0x40048158: __builtin_vec_new (vg_clientfuncs.c:156)
==22728== by 0x402DC10B: struct_type::struct_type(type_ops, int, char *, unsigned int) (types.cc:1745)
==22728== by 0x80C8885: loadType(void) (load.cc:186)
==22728== by 0x80C8BDD: loadTypes(void) (load.cc:237)
What is the sound of 0 bytes leaking?