HP OpenVMS Systems

Failures (memory leak, ACCVIO) in BACKUP API?

» close window

The Question is:

 
I've written a program in c using the BACKUP api. Essentially the program
hibernates until a specified time and then uses BACKUP to copy a directory
structure "device:[*]*.dir;" into a saveset. It then copies the save-set
over a tcp socket to a remote sy
stem. The remote system then explodes the save-set. It then hibernates again
and the cycle continues.
 
If <CTRL/T> is pressed after the first call to the api has completed, an
access violation occurs. If <CTRL/T> is pressed while the BACKUP api is
called on subsequent occasions, multiple BACKUP "last file scanned" messages
are displayed, instead of the nor
mal single message. Is this a bug in BACKUP ?
 
Memory leak in BACKUP ? After the first BACKUP cycle, the number of virtual
pages in use is 8913. After 6 cycles the process virtual page count has
risen to 20958 and an access violation occurs. BACKUP has been copying an
unmodified directory structure. T
he number of virtual pages in use only increases during calls to the BACKUP
api. I am not using the fast file scan option.
 
If these are bugs, will then and when will they be fixed ?
 
 

The Answer is :

 
  Please contact the Compaq Customer Support Center -- an example of the
  failing program and the particular stackdump will likely be required.
 

  

     

     
answer written or last revised on ( 19-AUG-1999 )
     
» close window