Re: Release works, Debug (still) crashes on OS X Leopard, Xcode 3.0 (Part 2) [SOLVED]

[Graham Reitz]

Thanks Jon,

Ahh...so the problem is with mixing debug and release builds with  
release libraries?  That makes sense.

I thought, since mysql++ doesn't come with a debug build, that it  
shouldn't matter.  Whose going to write an application and not use  
debug mode for at least a little while?

Is the intention when using the mysql++ dylibs that we will never need  
to build in debug mode?  I am a little confused here.  I know with the  
boost libs the default build creates both the debug and release libs.   
Why doesn't mysql++?  Is this some mysqlclient limitation?

thanks again,
graham

On Dec 5, 2007, at 3:24 PM, Jonathan Wakely wrote:

> On 05/12/2007, Warren Young <mysqlpp@stripped> wrote:
>> 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 the code definitely doesn't violate any STL preconditions then that
> could be the problem. you can't mix and match debug mode objects with
> non-debug mode objects if you pass types such as std::string or
> std::vector between objects.
>
>>> 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".
>
> That's intentional.
>
> Jon
>
> -- 
> MySQL++ Mailing List
> For list archives: http://lists.mysql.com/plusplus
> To unsubscribe:    http://lists.mysql.com/plusplus?unsub=1
>