Re: [Quantlib-dev] QuantLib linking causes debugger crash on OS X whether QuantLib used or not.

[Keith W. <kw...@gm...>]

Tamas,
   Here is what I did and got the same result.



qlTest.cpp and qlTest2.cpp are the same program.

The difference between the two build scripts is obvious. All  
references to QuantLib in qlTestBuild2.sh have been taken out.

The executables both run fine from the command line.

The qlTest program crashes the debugger:

The info.plist files (I don't know what Mac OSX does with the "*.dSYM"  
directory structure) differ so I am including them here as well:

  (I hope the naming is obvious here).

The only think I can think of that might be a little different is that  
I "built" boost. In other words I did the section 5.1 part of the  
boost installation page.

I have checked and I think I have the latest version of Xcode as well:

Here is the g++ version info:

/Users/kw/MyC++/boost_1_38_0 $ g++ -dumpversion
4.0.1

/Users/kw/MyC++/boost_1_38_0 $ g++ -version
i686-apple-darwin9-g++-4.0.1: no input files

And the gdb version info is in the debuggerCrash.txt file above.

If there is something else that will help you help me please let me  
know.

I really appreciate the help. I am also posting this to the quantlib- 
dev list (if it goes through).

Thanks so much for your time and in advance for any future help!

KW



--

On Mar 5, 2009, at 3:45 AM, Tamas Sashalmi wrote:

> Hello Keith,
>
> I cannot reproduce your problem, please make sure you are using the  
> newest
> xcode (it comes with updated gdb, gcc etc):
>
> http://developer.apple.com/technology/xcode.html
>
> Also please compile your example code from terminal instead of  
> eclipse.
> (eclipse may use a special flag which cause the problem ) with -g  
> flag  only
> eg:
>
> g++ -o prgname  -g prgsrc.cc -L/usr/local/lib -lQuantLib
> and see if gdb is working or not with the produced binary.
>
> Best,
>
> Tamas