topic Re: Re: Microsoft Visual C runtime library error R6034 in Kinetis Design Studio

Microsoft Visual C runtime library error R6034

matherinewang — Mon, 11 Aug 2014 01:25:12 GMT

Hi,

When i debug with KDS, i always have the following issue, but still can debug normally.

And the arm-none-eabi-gdb.exe can be found in the path: C:\Freescale\KDS_1.1.0\toolchain\bin.

BlackNight — Mon, 11 Aug 2014 04:52:07 GMT

Hello,

So it seems it cannot load/find a DLL/library correctly.

Can you try the dependency walker (Dependency Walker (depends.exe) Home Page) utility and check what DLL's are missing/not found?

It should produce an output something like this for C:\Freescale\KDS_1.1.0\toolchain\bin\arem-none-eabi-gdb.exe:

Erich

matherinewang — Tue, 12 Aug 2014 03:08:47 GMT

Hello Erich, Thanks for your quick respose every time!

I open the arem-none-eabi-gdb.exe in Dependency Walker, it shows as below. Is it means cannot load/find DLL/library correctly?

For example GPSVC.dll, it shows error opening file and cannot find it, but i can saw GPSVC.dll in the path: C:\Windows\System32.

BlackNight — Fri, 15 Aug 2014 10:25:34 GMT

Hmm, that looks very similar (actually, the same) as I have.

I think somehow a software on your system has installed an incompatible msvcr90.dll which is causing that problem.

So here is what you could check:

1. If you do not already have this, download and install the Process Explorer (Process Explorer) from the Windows Sysinternals

2. Start a debug session with KDS so that arm-none-eabi-gdb.exe to reproduce that that "Runtime Error! R6084" dialog.

3. Start the Process Explorer.

4. Enable DLLs for the lower pane view:

5. Locate and select arm-none-eabi-gdb.exe:

6. In the lower pane you should have several MSVCR*.dll you need to check

7. The MSVCR90.dll should be loaded from WinSxS

The other I have is from syswow64:

What I think is that one of these DLL's on your system are loaded from somewhere else?

Especially check for the one which is not loaded from WinSxS, and make a note of that path.

8. Close the debugging session, so that the gdb is not running any more. Now check that Dll for the KDS executable:

I guess one or the other points to a different path/tool (e.g. from your virus scanner, or any other utility).

That way you hopefully can identify the offending utility.

I guess that this offending utility has added the path to itself into your PATH system variable.

You could try if moving that offending utility path to the end of the PATH variable.

I hope this helps,

Erich

matherinewang — Mon, 18 Aug 2014 02:59:09 GMT

Hi Erich,

Thanks very very much, it solved my problem perfectly! I must salute to your professional and detail explaination. ^_^