topic Re: [BUG] access violation after dsymv call when debugging on AMD CPU in Intel® oneAPI Math Kernel Library

[BUG] access violation after dsymv call when debugging on AMD CPU

michaelkonecny — Thu, 25 Sep 2025 14:57:31 GMT

Hello,

this is likely related to ,
but the behaviour is slightly different, so I decided to report it too, in case it's caused by a different problem.

Versions used are the same: Visual Studio Community 17.14.14 and oneAPI 2024.1 on Windows.

When I build the bug reproducer from the aforementioned bug from the `direct_mkl_link-crash` branch:
https://bitbucket.org/k2fem/bug_intel_mkl_symv/src/direct_mkl_link-crash/
and run and debug the Debug configuration of the bug_mkl project, I get an access violation exception on line 21 of solve_sym_ldl_mod.f90:
```
if (info /= 0) b = IEEE_VALUE(b, IEEE_POSITIVE_INF)
```

The problem occured on an AMD CPU. I didn't try to reproduce it on an Intel unit.

This must be because dsymv corrupts the memory somehow beforehand. But maybe in a different manner still than what manifests itself in the first reported bug.

Just thought this should be reported.

Have a good day,
Michael

Re: [BUG] access violation after dsymv call when debugging on AMD CPU

michaelkonecny — Fri, 26 Sep 2025 13:16:02 GMT

Hello,

I retested this on oneAPI 2025.2.

I now get an access violation exception from inside the dsymv subroutine.
It manifests itself on both Debug and Release builds.
It also happens on both AMD and Intel CPUs.
The CPUs I tested it on were:
- AMD EPYC 7502P
- Intel Core i7-10750H

Therefore the issue is likely unrelated to and still needs to be addresseed.

Thank you

Re: [BUG] access violation after dsymv call when debugging on AMD CPU

michaelkonecny — Fri, 26 Sep 2025 13:17:57 GMT

The topic should be renamed to "[BUG] access violation after dsymv call" as it no longer seems to be debug-build or AMD specific.

Re: [BUG] access violation after dsymv call when debugging on AMD CPU

Fengrui — Mon, 27 Oct 2025 23:11:00 GMT

It looks the code is calling dsysv the way it should be calling dsysv_f95.