(In reply to Thomas Dickey from comment #5) > I'm puzzled because the patch affects the no-leaks code (which is used only > for analysis). Hmmm .. I'm not aware that libraries which are compiled with no-leak support do cause trouble ... in fact I'm using --disable-leaks at configure time [ 49s] checking if you want to perform memory-leak testing... yes