Hello Andreas Unfortunately I haven't figured out what causes this, so right now I'm just using the -O0 option for my release version. Do you have a simple code example which provokes this error? Then I can try to test it on previous versions of g++ Kinds regards Bjoern D. Rasmussen

From: akabel@stanford.edu To: "Bear" Subject: Re: Trouble using shared_ptr with g++ -O0 and -O2 options Date: Fri, 17 Dec 2004 12:06:37 -0800

...

Hello there

I'm getting a SIGSEGV when using the boost::shared_ptr in my program and compiling with the g++ -O2 option, whereas if I'm using the g++ -O0

Bear wrote: option

...

my programs works the way it should. My program is multi-threaded but to the best of my knowledge it is mutex'ed correctly.

I have a very similar problem in a (single-threaded) program. I tried several compilers; Intel icc v8.0 behaves correctly, even for high optimization level, gcc 3.4 and gcc 3.3 dump core at -O2 and behave correctly at -O0. Did you find out what causes this?

Thanks,

Andreas

_________________________________________________________________ Del din verden med MSN Spaces http://spaces.msn.com