The SAS® git_index_add function returns a segmentation stack


When you use the git_index_add function to stage files, a segmentation violation error stack occurs if the status argument is missing.

Here is an example of the function without the status argument:

data null;
    rc=git_index_add ("/some/path/to/repository", "test.sas");
    put rc=;
run;

This code returns the following:
 
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
 
The SAS task name is [DATASTEP]
Segmentation Violation
 
Traceback of the Exception:
 
/sas94/install/SASFoundation/9.4/sasexe/sas(+0x17d5fe) [0x560c829555fe]
/sas94/install/SASFoundation/9.4/sasexe/sas(+0x503be) [0x560c828283be]
/sas94/install/SASFoundation/9.4/sasexe/tkmk.so(bkt_signal_handler+0x14b) 
[0x7f15a115c2db]

/usr/lib64/libpthread.so.0(+0x12dc0) [0x7f15a299fdc0]
/sas94/install/SASFoundation/9.4/sasexe/uwugit_i(add_files_to_index+0x27c) 
[0x7f15489253bc]

[0x7f154ad0669a]
 
A hot fix for this issue has been released in SAS® 9.4M9 (TS1M9) to include an intuitive error message, which states that the user is missing an argument instead of a Segmentation Violation error.