Hi Cody,
Thank you so much.
I will probably go with devel mode for now, but this is very good to know.
Thank you especially for the details so that I can try your options as soon as
devel mode does not help me any further.
-Anna
On 10 Sep 2010, at 17:24, Cody Permann wrote:
> Hum - XC
Hum - XCode 3.2.3...
Apple made some significant changes in their linker beginning in version 3.2.2.
Significant enough that all of our Intel compiled builds started Seg faulting
for those who clicked the automatic update from Apple. I didn't do extensive
testing with GNU at the time but inst
On Fri, 10 Sep 2010, Anna-Lena Gerner wrote:
>> In that case, would you try using a custom compilation method? Try
>> building (after a clean) in devel mode, but with a CXXFLAGS
>> environment variable set to include "-D_GLIBCXX_DEBUG
>> -D_GLIBCXX_DEBUG_PEDANTIC"
>>
>> If that breaks, then it'
> In that case, would you try using a custom compilation method? Try
> building (after a clean) in devel mode, but with a CXXFLAGS
> environment variable set to include "-D_GLIBCXX_DEBUG
> -D_GLIBCXX_DEBUG_PEDANTIC"
>
> If that breaks, then it's probably some problem specific to your OS X
> GCC
On Fri, 10 Sep 2010, Anna-Lena Gerner wrote:
> I have just tried devel mode, and, same as in opt mode, everything seems to
> be perfectly fine here ...
In that case, would you try using a custom compilation method? Try
building (after a clean) in devel mode, but with a CXXFLAGS
environment var
On 10 Sep 2010, at 12:34, Roy Stogner wrote:
>
>
>>> On Sep 4, 2010, at 10:29 AM, Anna-Lena Gerner wrote:
>>>
I installed libMesh on my Mac OS X, and in opt mode everything is just
fine. There also seem to be no compilation problems in dbg mode. However,
in dbg mode I get the
>> On Sep 4, 2010, at 10:29 AM, Anna-Lena Gerner wrote:
>>
>>> I installed libMesh on my Mac OS X, and in opt mode everything is just
>>> fine. There also seem to be no compilation problems in dbg mode. However,
>>> in dbg mode I get the following runtime error: (./ex4-dbg -d 1 -n 20)
>>>
>>> #
On 7 Sep 2010, at 09:44, Cody Permann wrote:
>
> On Sep 4, 2010, at 10:29 AM, Anna-Lena Gerner wrote:
>
>>
>> Hi everybody,
>>
>> I installed libMesh on my Mac OS X, and in opt mode everything is just fine.
>> There also seem to be no compilation problems in dbg mode. However, in dbg
>> mod
On Sep 4, 2010, at 10:29 AM, Anna-Lena Gerner wrote:
>
> Hi everybody,
>
> I installed libMesh on my Mac OS X, and in opt mode everything is just fine.
> There also seem to be no compilation problems in dbg mode. However, in dbg
> mode I get the following runtime error: (./ex4-dbg -d 1 -n 20)
>
> Whenever I see a segfault coming from a weird place, in this case,
> from the destructor of std::string, I usually suspect an incomplete
> recompile of some sort. For example, object files from an older
> compiler version getting linked with object files from a new one, etc.
> Can you see if
On Sat, Sep 4, 2010 at 11:29 AM, Anna-Lena Gerner
wrote:
>
> Hi everybody,
>
> I installed libMesh on my Mac OS X, and in opt mode everything is just fine.
> There also seem to be no compilation problems in dbg mode. However, in dbg
> mode I get the following runtime error: (./ex4-dbg -d 1 -n 20
Hi everybody,
I installed libMesh on my Mac OS X, and in opt mode everything is just fine.
There also seem to be no compilation problems in dbg mode. However, in dbg mode
I get the following runtime error: (./ex4-dbg -d 1 -n 20)
ex4-dbg(73819) malloc: *** error for object 0x1032e6fa0: pointer
12 matches
Mail list logo
