mesa-users] Missing a tmp.txt file in the kap module?

[Eric Blais]

Hi,

Here's what I get:

forrtl: severe (174): SIGSEGV, segmentation fault occurred
> Image              PC                Routine            Line
> Source
> tester             00000000004218A8  load_co_kap_mp_re         515
> load_co_kap.f
> tester             000000000041FE89  load_co_kapprepar         388
> load_co_kap.f
> tester             000000000041E579  load_co_kap_mp_pr         209
> load_co_kap.f
> tester             0000000000424F20  load_co_kap_mp_lo          95
> load_co_kap.f
> tester             0000000000429532  kap_eval_co_mp_ge         648
> kap_eval_co.f
> tester             0000000000428C08  kap_eval_co_mp_ge         373
> kap_eval_co.f
> tester             00000000004281FF  kap_eval_co_mp_ge         107
> kap_eval_co.f
> tester             000000000041D1E5  kap_eval_mp_get_k          96
> kap_eval.f
> tester             00000000004161B5  kap_lib_mp_kap_ge         196
> kap_lib.f
> tester             0000000000404041  test_kap_support_         111
> test_kap_support.f
> tester             0000000000403C7C  test_kap_support_          38
> test_kap_support.f
> tester             0000000000415EB3  MAIN__                      6
> test_kap.f
> tester             0000000000403BEC  Unknown               Unknown  Unknown
> libc.so.6          00000030C381D994  Unknown               Unknown  Unknown
> tester             0000000000403AF9  Unknown               Unknown  Unknown
>

Out of curiosity I ran rn again and it actually got a bit further this time:

 test number           1
 fixed metals

                                    logT    6.0000000000000000E+00
                                  logRho   -6.0000000000000000E+00
                                   zbase    1.0000000000000000E-02
                                      xh    6.9999999999999996E-01
                                     dxc    0.0000000000000000E+00
                                     dxo    0.0000000000000000E+00

                                log10kap   -4.4899999621474185E-01
                           dlnkap_dlnRho    1.9495729357004166E-02
                             dlnkap_dlnT    2.8335783630609512E-02

                                     kap    3.5563132166862488E-01
                               dkap_dlnd    6.9332919981252017E-03
                               dkap_dlnT    1.0077092183069847E-02

forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC                Routine            Line
Source
tester             00000000004218A8  load_co_kap_mp_re         515
load_co_kap.f
tester             000000000041FE89  load_co_kapprepar         388
load_co_kap.f
tester             000000000041E579  load_co_kap_mp_pr         209
load_co_kap.f
tester             0000000000424F20  load_co_kap_mp_lo          95
load_co_kap.f
tester             0000000000429532  kap_eval_co_mp_ge         648
kap_eval_co.f
tester             0000000000428C08  kap_eval_co_mp_ge         373
kap_eval_co.f
tester             00000000004281FF  kap_eval_co_mp_ge         107
kap_eval_co.f
tester             000000000041D1E5  kap_eval_mp_get_k          96
kap_eval.f
tester             00000000004161B5  kap_lib_mp_kap_ge         196
kap_lib.f
tester             0000000000404041  test_kap_support_         111
test_kap_support.f
tester             0000000000403C7C  test_kap_support_          38
test_kap_support.f
tester             0000000000415EB3  MAIN__                      6
test_kap.f
tester             0000000000403BEC  Unknown               Unknown  Unknown
libc.so.6          00000030C381D994  Unknown               Unknown  Unknown
tester             0000000000403AF9  Unknown               Unknown  Unknown


Sadly, running it again doesn't improve the situation further.

Cheers,
Eric Blais


On Fri, Jun 25, 2010 at 11:54 AM, Bill Paxton <paxton at kitp.ucsb.edu> wrote:

>
> On Jun 25, 2010, at 7:59 AM, Eric Blais wrote:
>
> > <log.txt>
>
> Hi,
>
> Thanks for sending the log.   Please do this:
>
> cd mesa/kap/test
> ./rn
>
> Then send the terminal output from that.
> We need to find out what is causing the "FAILED" message.
>
> Thanks,
> Bill
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.mesastar.org/pipermail/mesa-users/attachments/20100625/35cc8b24/attachment.html>