Skip to content
This repository was archived by the owner on Feb 8, 2022. It is now read-only.
This repository was archived by the owner on Feb 8, 2022. It is now read-only.

Namespace conflict for try_reading_model() #111

@scallag

Description

@scallag

When trying to create a mesh using CS173, I experienced a seg fault. Looking at the core file, it appears the CS173 library is trying to call try_reading_model() from the CCA library:

(gdb) where
#0 0x00002aaabf2330e6 in try_reading_model ()
from /projects/sciteam/baln/CyberShake/software/UCVM/ucvm-18.5.0_07282018/model/cca/lib/libcca.so
#1 0x00002aab97e60c6d in cs173_init (
dir=0x7fffffff38d8 "/projects/sciteam/baln/CyberShake/software/UCVM/ucvm-18.5.0_07282018", label=0x7fffffff3860 "cs173")
at cs173.c:46
#2 0x0000000000410240 in ucvm_plugin_model_init (id=0, conf=0x7fffffff3860) at ucvm_model_plugin.c:111
#3 0x000000000040a66e in ucvm_add_user_model (m=m@entry=0x7fffffff3620, mconf=mconf@entry=0x7fffffff3860) at ucvm.c:529
#4 0x000000000040ab22 in ucvm_add_model (label=, label@entry=0x448cbf "cs173") at ucvm.c:484
#5 0x000000000040aeb8 in ucvm_add_model (label=label@entry=0x448cbf "cs173") at ucvm.c:485
#6 0x0000000000405d15 in main (ac=14, av=0x7fffffff5308) at ucvm-single_mpi.c:513

Upon further investigation, it seems that both CCA and CS173 have try_reading_model() functions. I think changing the name of one of these functions would resolve the issue.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions