Memory access violation on running test suite

[Richard Stanton]

I just downloaded QuantLib 1.4 and installed it on my Mac (OS X 10.9.2)
following the instructions at http://quantlib.org/install/macosx.shtml.
The compilation completed fine, but when I try to run quantlib-test-suite,
I get the error

  Test setup error: memory access violation at address: 0x00000029: no
mapping at fault address


Am I missing something?

Thanks.

Richard Stanton


------------------------------------------------------------------------------
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users

[Richard Stanton]

Richard Stanton <stanton <at> haas.berkeley.edu> writes:
 
>   Test setup error: memory access violation at address: 0x00000029: no
> mapping at fault address

Running the same procedure on my home machine, everything works fine. The
only difference I'm aware of is that my office machine runs OS X 10.9.2, while
my home machine runs 10.8.5. Could this be relevant?


------------------------------------------------------------------------------
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users

[Richard Stanton]

Switching back to the default clang rather than Mac Ports gcc 4.8,
it all runs fine now, with no errors reported in the test suite. It may
well have something to do with using a precompiled Mac Ports
version of the boost libraries (though why the same setup works
on my home machine I don't know).


------------------------------------------------------------------------------
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users

[Dirk Eddelbuettel]

On 27 March 2014 at 20:53, Richard Stanton wrote:
| Switching back to the default clang rather than Mac Ports gcc 4.8,
| it all runs fine now, with no errors reported in the test suite. It may
| well have something to do with using a precompiled Mac Ports
| version of the boost libraries (though why the same setup works
| on my home machine I don't know).

That is the likely culprit.

 If you switch toolchains you probably need to sure all the libraries you
touch (ie C++ library, Boost, QuantLib) are built consistently.  

QuantLib 1.4 is not that far from 1.3 and 1.2, and all those versions have
been rather solid all those years.

Dirk

--
Dirk Eddelbuettel | [hidden email] | http://dirk.eddelbuettel.com

------------------------------------------------------------------------------
_______________________________________________
QuantLib-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/quantlib-users