On 22 May 2011 15:16, Ruben Safir <ru...@mrbrklyn.com> wrote: > On Sun, May 22, 2011 at 02:29:08PM +0100, Jonathan Wakely wrote: >> re http://gcc.gnu.org/ml/gcc-bugs/2011-05/msg01899.html >> >> The gcc-bugs mailing list is for mails automatically generated by >> bugzilla, if you want to report a bug please do so in bugzilla, not by >> email. See http://gcc.gnu.org/bugs/ for instructions. >> >> If you want to ask for help using g++ then use the gcc-help mailing >> list, see http://gcc.gnu.org/lists.html >> > > > Can't be done. It's not working, aside from the fact that this is too > complex of an example to fit within the parameters.
It's working fine for me. As for too complex: nonsense. Did you bother to read the link I provided? You can attach preprocessed source, though you should really try to reduce it to a minimal testcase - I don't believe mysql++ is really necessary to demonstrate the problem. None of that changes the fact gcc-bugs is the wrong list. > I spent nearly 45 minutes gathering all the information together. If > the post is not adequate, that is fine. That's why i don't report bugs. Run your code under valgrind, it shows you were the first memory corruption occurs. If you don't want to report bugs then dont' be surprised if they don't get fixed.
