Brian, It's bad news to know that the program runs without optimizations but fails when compiled with optimizations: that either means the program is incorrectly doing something undefined, that leads to this different behaviour, or that some of the optimizations performed by the compiler are wrong.
Before accusing the compiler, I need to rule out any problem in the code itself. This is why I need you to run a test where the whole program is optimized, and only the src/lib/xmalloc.c file is compiled without optimizations. Indeed, there is a possibility that the malloc() data structures are corrupted outside, and of course the malloc() code will then discover the inconsistency and fail, but that does not mean the bug is in the malloc() code itself. If you change the whole program to run without optimizations, you can remove this accidental corruption source and then the program runs normally, of course. Not doing the test means I cannot investigate this bug further, since I am unable to reproduce the failure here, even when compiling with -O3. Cheers, Raphael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
