Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

be careful mixing versions of CasaCore #53

Open
mweastwood opened this issue Mar 16, 2016 · 1 comment
Open

be careful mixing versions of CasaCore #53

mweastwood opened this issue Mar 16, 2016 · 1 comment

Comments

@mweastwood
Copy link
Owner

This issue is a warning/reminder for myself until this is better documented.


When copying a measurement set between machines I got a segfault when trying to create a new column:

signal (11): Segmentation fault
_ZN4casa7SSMBase12removeColumnEPNS_17DataManagerColumnE at /scr2/mweastwood/usr/lib/libcasa_tables.so.2 (unknown line)
_ZN4casa9ColumnSet11doAddColumnERKNS_10ColumnDescEPNS_11DataManagerE at /scr2/mweastwood/usr/lib/libcasa_tables.so.2 (unknown line)
_ZN4casa9ColumnSet9addColumnERKNS_10ColumnDescEbRKNS_9TSMOptionERNS_5TableE at /scr2/mweastwood/usr/lib/libcasa_tables.so.2 (unknown line)
_ZN4casa10PlainTable9addColumnERKNS_10ColumnDescEb at /scr2/mweastwood/usr/lib/libcasa_tables.so.2 (unknown line)
_ZN4casa5Table9addColumnERKNS_10ColumnDescEb at /scr2/mweastwood/julia-packages/v0.4/CasaCore/src/../deps/libcasacorewrapper.so (unknown line)
_Z15addScalarColumnIiEvPN4casa10TableProxyEPc at /scr2/mweastwood/julia-packages/v0.4/CasaCore/src/../deps/libcasacorewrapper.so (unknown line)
addScalarColumn_int at /scr2/mweastwood/julia-packages/v0.4/CasaCore/src/../deps/libcasacorewrapper.so (unknown line)
create_column! at /scr2/mweastwood/julia-packages/v0.4/CasaCore/src/tables.jl:259
Segmentation fault (core dumped)

It seems that the problem is that the measurement set was created on a machine with CasaCore v1.7 and I was trying to add a new column with a machine that is using CasaCore v2.0. So we need to be careful and consistent about which version we are using.

@tammojan
Copy link
Contributor

This should not happen. When a measurement set is written, it should be readable by all versions of casacore. Could it be that you had two versions of casacore on the same machine, and a shared library of a different version was found at runtime?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants