Potential Buffer overwrite in DGEEV when compiled in a debug mode.

Hi, 

We recently upgrade our MKL to version 18.3 and TBB to version 18.4. When running a debug version of our code we noticed that we were getting heap corruption when calling the DGEEV MKL function. It appears that the work vector passed into the function was overwritten. Importantly, one can query for the optimum length of the work vector by passing in -1 as the length of the work vector. In this particular case, we have a 60x60 input matrix and the optimum length of the work vector was returned as 2040. However, we were passing in a value of 6x60 = 360 for the work vector. After running DGEEV in debug mode, it appears that the function was assuming the length of the work vector was the optimum length as all of the data up to that length (2040) had been modified. 

When running a release version of our application, the DGEEV function did not write beyond the specified length vector of 360. 

I then created a console application that loads the input matrix from a file and then calls the DGEEV function. The behavior mentioned above showed the potential heap corruption on the work vector. 

Is this a known issue? If so, are there any other MKL functions that we must worry about?

Thanks in advance for your response. 

Murray

P.S. I realize that querying the function for the optimum work vector length is a workaround.