16 messages in com.mysql.lists.plusplusRe: Release works, Debug (still) cras...
FromSent OnAttachments
Graham Reitz03 Dec 2007 19:25 
Graham Reitz04 Dec 2007 20:46 
Graham Reitz04 Dec 2007 21:00 
Warren Young05 Dec 2007 08:17 
Jonathan Wakely05 Dec 2007 13:22 
Jonathan Wakely05 Dec 2007 13:24 
Graham Reitz05 Dec 2007 14:42 
Jonathan Wakely05 Dec 2007 15:02 
Warren Young05 Dec 2007 16:55 
Graham Reitz05 Dec 2007 20:08 
Graham Reitz05 Dec 2007 21:19 
Graham Reitz06 Dec 2007 15:16 
Graham Reitz06 Dec 2007 15:22 
Jonathan Wakely06 Dec 2007 15:44 
Graham Reitz07 Dec 2007 12:20 
Warren Young09 Jan 2008 20:08 
Subject:Re: Release works, Debug (still) crashes on OS X Leopard, Xcode 3.0 (Part 2) [SOLVED]
From:Warren Young (mysq@etr-usa.com)
Date:12/05/2007 08:17:14 AM
List:com.mysql.lists.plusplus

Graham Reitz wrote:

When you create a C++ Command Line Tool project in Xcode 3.0 it adds the following preprocessor defines:

_GLIBCXX_DEBUG=1 _GLIBCXX_DEBUG_PEDANTIC=1

When these are there it crashes in debug mode.

The mighty Google says these flags turn on internal debugging within the standard libraries, or at least within STL.

It may be that you have to use these flags for all modules within the project, which wouldn't happen if you're building MySQL++ using the standard configure && make && make install pattern.

If you did indeed build MySQL++ this way, try this:

$ cd /mysqlpp/directory $ make clean $ ./configure CXXFLAGS="_GLIBCXX_DEBUG=1 _GLIBCXX_DEBUG_PEDANTIC=1" $ make && sudo make install

This would be the "debug version" you sought after earlier, though there is no way to distinguish it from a release version from the outside.

Even if I set the to =0 it still crashes.

Clearly some code is using #if defined(X) or #ifdef X instead of #if X to decide whether this flag is "on".