Closed ponweist closed 10 years ago
Last lines in 16sm.wpout:
...
Time to read and process 0.036 (sec)
Reading uHu overlaps from 16sm.uHu in get_CC_R: Created on 31Jul2014 at 16:31:41
before CC loop
Job output:
DISK GROUP QUOTAS for home and project file systems:
Filesystem Quota Used Space Free Space
/home/hpc/pr87xo ($HOME) 100.0GB 2.8GB ( 3%) 97.2GB (97%)
/gpfs/work/pr87xo ($WORK) 900.0GB 250.1GB (28%) 649.9GB (72%)
-------------------------------------------------------------------------------
Executing LRZ User Prolog ...
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
libirc.so 00002B542692C2C9 Unknown Unknown Unknown
libirc.so 00002B542692AB9E Unknown Unknown Unknown
postw90.x 0000000001152A72 Unknown Unknown Unknown
postw90.x 000000000110B083 Unknown Unknown Unknown
postw90.x 000000000110F05B Unknown Unknown Unknown
libmonitor.so 00002B54257CC90E Unknown Unknown Unknown
libpthread.so.0 00002B54259F9810 Unknown Unknown Unknown
postw90.x 00000000004644F0 Unknown Unknown Unknown
postw90.x 00000000004B66FD Unknown Unknown Unknown
postw90.x 0000000000414085 Unknown Unknown Unknown
postw90.x 0000000000413F36 Unknown Unknown Unknown
libmonitor.so 00002B54257C7302 Unknown Unknown Unknown
libc.so.6 00002B5426D9DC16 Unknown Unknown Unknown
libmonitor.so 00002B54257C6ABE Unknown Unknown Unknown
postw90.x 0000000000413E29 Unknown Unknown Unknown
real 0m13.581s
user 0m16.669s
sys 0m2.852s
Reason for segmentation fault was (as reported by enabling runtime checks):
forrtl: severe (408): fort: (7): Attempt to use pointer OO_R when it is not associated with a target
Fixed in 35e705238863b176c6f00f02190413c05da24779. Rerun all testcases - output files seem to be o.k.
A segmentation fault occurs when running testcase A of issue #8 with the code verision 37e249c6ff9939e5a2f322cdc10663dc23d7523f.
Running it with the previous version, 0c9e71ec935110e01957884dfa98bfd6c5376323, works.