Opened 2 weeks ago
data ingestion with directql has a segfault
|Reported by:||bbell||Owned by:||bbell|
|Keywords:||directql, ingest, segfault||Cc:||dmisev|
In directql.cc, in the doStuff() function, there seems to be some issues with the way in which the char* pointer named fileContents is handled.
Ideally, the use of smart pointers (e.g. shared_ptr and unique_ptr) could be implemented in this section of code. A simpler, albeit more rudimentary, fix could be to copy the way that memory allocation is handled in rasql.cc's doStuff() function; however, it is important to keep in mind that these functions work differently!
trace for the problem:
rasql -q 'create collection test_tmp GreySet?' --user <> --passwd <>
valgrind directql -q 'insert into test_tmp values decode($1)' -f mr_1.png --user <> --passwd <>
you should get 5-6 errors here, but resolving the problem in directql.cc should fix all but 1-2 of them.