| Author | Topic: Debug errs in Win-10 |
---|
| Itai Ben-Artzi | Debug errs in Win-10
on Sun, 10 Jan 2016 00:38:20 -0800I just moved from Win-7 to Win-10, installed Alaska, and perform the most
recent update (build 656). The workbench, compiler, and linker work well,
but debug does not run and the following error is displayed:
DBG: Client has exited (Code: -1073741515, Possible DLL version conflict).
Please advice on how to fix this (also, a more descriptive error would help
both, Alaska and us).
Many thanks,
-Itai |
| Peter Alderliesten | Re: Debug errs in Win-10
on Mon, 11 Jan 2016 11:36:42 +0100Itai,
> I just moved from Win-7 to Win-10, installed Alaska, and perform the most
> recent update (build 656). The workbench, compiler, and linker work well,
> but debug does not run and the following error is displayed:
> DBG: Client has exited (Code: -1073741515, Possible DLL version conflict).
>
> Please advice on how to fix this (also, a more descriptive error would help
> both, Alaska and us).
You could try the command line debugger. There's a good chance that you
will get another error description there.
Peter |
| Itai Ben-Artzi | Re: Debug errs in Win-10
on Wed, 13 Jan 2016 00:35:17 -0800Peter,
The command line (xppdbg) works, but the debug from the workbench errs on my
Win-10.
Any idea on how to get it to work?
-Itai |
| Itai Ben-Artzi | Re: Debug errs in Win-10
on Wed, 13 Jan 2016 15:08:45 -0800Eureka!
The benchmark debugger looks into the Lib folder for DLLs, not into Runtime.
I’ve changed the settings to include Runtime in the environment settings and
all is well now.
-Itai |