On Nov 24, 2009, at 8:23 PM, Martin Costabel wrote:
> Ben Abbott wrote:
> []
>> Is it possible that the wrong dylib is being loaded at run time? Is there a
>> way to (safely) test the idea?
>
> The other libstdc++ is loaded because it is pulled in by some of the dylibs
> liboctinterp-3.3.50+.d
Ben Abbott wrote:
[]
> Is it possible that the wrong dylib is being loaded at run time? Is there a
> way to (safely) test the idea?
The other libstdc++ is loaded because it is pulled in by some of the
dylibs liboctinterp-3.3.50+.dylib links to, for example
/sw/lib/fltk-aqua/lib/libfltk_gl.1.1.d
On Nov 23, 2009, at 4:39 PM, Martin Costabel wrote:
> Ben Abbott wrote:
>> On Nov 22, 2009, at 10:09 AM, Martin Costabel wrote:
> []
>>> Did the CrashReporter write something in ~/Library/Logs?
>>>
>> []
>> The file below is from ~/Library/Logs/DiagnosticReports.
>
> I don't really know what's
Ben Abbott wrote:
> On Nov 22, 2009, at 10:09 AM, Martin Costabel wrote:
[]
>> Did the CrashReporter write something in ~/Library/Logs?
>>
>[]
> The file below is from ~/Library/Logs/DiagnosticReports.
I don't really know what's going on; I can only speculate.
What looks suspicious to me is the f
On Nov 22, 2009, at 10:09 AM, Martin Costabel wrote:
> Ben Abbott wrote:
>> On Nov 21, 2009, at 4:25 PM, Martin Costabel wrote:
>>> Ben Abbott wrote:
>>> []
> Program received signal EXC_BAD_ACCESS, Could not access memory.
> Reason: KERN_PROTECTION_FAILURE at address: 0x
> 0x
Ben Abbott wrote:
> On Nov 21, 2009, at 4:25 PM, Martin Costabel wrote:
>
>> Ben Abbott wrote:
>> []
Program received signal EXC_BAD_ACCESS, Could not access memory.
Reason: KERN_PROTECTION_FAILURE at address: 0x
0x02c0702f in std::locale::operator= ()
(gdb)
>> Maybe a
On Nov 21, 2009, at 4:25 PM, Martin Costabel wrote:
> Ben Abbott wrote:
> []
>>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>>> Reason: KERN_PROTECTION_FAILURE at address: 0x
>>> 0x02c0702f in std::locale::operator= ()
>>> (gdb)
>
> Maybe a backtrace "bt" would give
Ben Abbott wrote:
[]
>> Program received signal EXC_BAD_ACCESS, Could not access memory.
>> Reason: KERN_PROTECTION_FAILURE at address: 0x
>> 0x02c0702f in std::locale::operator= ()
>> (gdb)
Maybe a backtrace "bt" would give some more insight.
--
Martin
On Nov 17, 2009, at 3:53 AM, Martin Costabel wrote:
>
>> [I migrated my 10.5 Fink to 10.6 (using 32bit), and deleted my static libs
>> left over from 10.5, and rebuilt them as needed]. Octave does build, but
>> when I try to run it ... $ ./run-octave
>> Bus error
>
> Now this is a different st
