Nirva Application Platform

here is demonstration Java procedure that produces the issue:

//import com.nirvasoft.nirva.nvcmd;
import com.nirvasoft.nirva.nvsint;
/* PROCEDURES */
class test_truncate
{
 public static int main()
 {
  nvsint ProcCMD;

  // Procedure Class
  ProcCMD = new nvsint();

  if(ProcCMD == null)
  {
     System.out.print("Error getting nvinst class\n");
     return -1;
  }  
  // Create a INDSTRINGLIST 
  ProcCMD.Command("NV_CMD=|OBJECT:CREATE| TYPE=|INDSTRINGLIST| NAME=|TRUNCATE_EXMP| REPLACE=|YES|");
  // Add a Few Values
  for (int i=0; i<100; i++)
  {
   ProcCMD.Command("NV_CMD=|OBJECT:INDSTRINGLIST_SET_VALUE| NAME=|TRUNCATE_EXMP| KEY=|SOME_LONG_KEY_NAME_"+Integer.toString(i)+"_WITH_NO_DESCRIPTION_BLAH_BLAH| VALUE=|SOME_SILLY_LONG_VALUE_"+Integer.toString(i)+"_WITH_NO_DESCRIPTION_BLAH_BLAH|");
  }
  ProcCMD.Command("NV_CMD=|OBJECT:INDSTRINGLIST_GET_VALUES| MODE=|STRING| NAME=|TRUNCATE_EXMP|");
  System.out.println(ProcCMD.NvResult);

  return 0;
 }
}
The output returned to the console ends with "=SOME_SILLY_VALUE_9_WITH_NO_DESCRIPTION_BLAH_BLA" and interestingly its only the last character that is missing! the whole output this generates is only 10678 chars long, so I was wondering if your using malloc if maybe the calculation to extend the field hasn't taken into account the string null terminator or something?