rasgeo segfault on non-matching types

[Dimitar Misev]

When the given MDD/set types with the -t parameters are different from the image type (I did it by mistake), rasgeo segfaults. It's no big deal, but I put it in a ticket so we don't forget it.

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff3eace30 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
(gdb) bt
#0  0x00007ffff3eace30 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x000000000045c202 in RasdamanHelper2::rowBuf2ColBuf (this=0x7fffffffceb0, rowbuf=0x7fffe38cc010 "", colbuf=0x7fffc38da010 "", pixelsize=8, nelem=4, ncols=12319, nrows=5447, nlayers=1)
    at RasdamanHelper2.cxx:889
#2  0x000000000045a963 in RasdamanHelper2::updateImage (this=0x7fffffffceb0, collname=..., imgid=4609, buf=0x7fffe38cc010 "", shift=..., sdom=..., bRowMajor2ColMajor=true, marraytypename=...)
    at RasdamanHelper2.cxx:652
#3  0x0000000000459c9a in RasdamanHelper2::insertImage (this=0x7fffffffceb0, collname=..., buf=0x7fffe38cc010 "", shift=..., sdom=..., bRowMajor2ColMajor=true, marraytypename=...)
    at RasdamanHelper2.cxx:575
#4  0x0000000000411225 in importImage (helper=..., pDs=0x776f20, collname=..., oids=..., readGDALImgDOM=..., writeShift=..., newGeoRegion=..., asCube=false, marraytypename=...)
    at rimport.cxx:812
#5  0x000000000040f888 in processImageFiles (filenames=..., collname=..., oids=..., processRegion=..., mode3D=..., shiftPt=..., helper=..., marraytypename=...) at rimport.cxx:680
#6  0x0000000000415eaa in main (argc=7, argv=0x7fffffffd888) at rimport.cxx:1355

[herziga@…]

Hi Dimitar

I tried using TypeIterator<MDDType> and friends as done in rasdl::printNames() to query type information at runtime. But I was only able to use it as the user running rasmgr/rasserver . Using a different user, which has no problems importing images using rasgeo, I got access problems. That's why I came up with the -t parameter for rasgeo in the first place. Is this functionality somehow reserved to the actual rasdaman admin?

Alex

[Dimitar Misev]

Ah right, that functionality is actually server-side (rasdl is a server-side tool), that's why you need to use that user, and it wouldn't work if you use rasgeo from another machine.

[Dimitar Misev]

Deferring until type management is included in the client-server protocol of rasdaman.