Stopping due to fatal error: ArgumentException: An item with the same key has already been added. #8760

ninok · 2022-02-02T13:54:49Z

Bug type: Debugger

Describe the bug

OS and Version: MacOS 11.6.3 with remote ssh to Amazon Linux 2
VS Code Version: 1.63.2
C/C++ Extension Version: 1.8.3
Other extensions you installed (and if the issue persists after disabling them):
A clear and concise description of what the bug is.

I cannot execute any gdb command in the debug console anymore.
When I for example do -exec ptype geometry1
I get: Stopping due to fatal error: ArgumentException: An item with the same key has already been added. Key: (Microsoft.MIDebugEngine.AD7StackFrame, geometry1)
The variable name in the error message seems unrelated to my command. It also happens when I add breakpoints through debug console. It seems to always be the first local variable in the call stack that is mentioned in the error message.

Interesting to note though: The actual command succeeds and I can see the output of ptype. The error/crash happens just after.

Additional context
I cannot include full trace here for legal reasons.
Last messages before the crash are:

--> E (output): {"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/Evaluate","data":{"VS.Diagnostics.Debugger.ImplementationName":"Microsoft.MIDebugEngine","VS.Diagnostics.Debugger.EngineVersion":"17.1.20131.1","VS.Diagnostics.Debugger.HostVersion":"17.1.20131.1","VS.Diagnostics.Debugger.AdapterId":"cppdbg","VS.Diagnostics.Debugger.Evaluate.Duration":1615.0,"VS.Diagnostics.Debugger.Evaluate.IsError":false,"VS.Diagnostics.Debugger.Evaluate.ExecuteInConsole":true}},"seq":2275}
--> R (evaluate-25): {"type":"response","request_seq":25,"success":true,"command":"evaluate","body":{"result":"","variablesReference":0},"seq":2277}
<--   C (scopes-26): {"command":"scopes","arguments":{"frameId":1000},"type":"request","seq":26}
--> R (scopes-26): {"type":"response","request_seq":26,"success":true,"command":"scopes","body":{"scopes":[{"presentationHint":"locals","name":"Locals","variablesReference":1010,"expensive":false},{"presentationHint":"registers","name":"Registers","variablesReference":1011,"expensive":true}]},"seq":2280}
<--   C (variables-27): {"command":"variables","arguments":{"variablesReference":1010},"type":"request","seq":27}

The text was updated successfully, but these errors were encountered:

jmazar · 2022-02-02T15:18:33Z

I'm having the same error.

ruabmbua · 2022-02-02T16:11:27Z

Have the same error here. Seems like it is unsupported to have the same variable name twice in a stack frame, which is of course possible in e.g. C++

Renaming the duplicate variable names in nested blocks solves the debugger hang.

ruabmbua · 2022-02-02T16:24:46Z

Hm seems like there is something else going on as well. Only managed to debug a little further, but now the same error, but there are not multiple variables with same name on the same stack frame.

markrussell-cpu · 2022-02-02T16:32:43Z

I'm having the same errors.

ruabmbua · 2022-02-02T16:33:48Z

Strangely enough downgrading the extension does not help?

Edit: Managed to downgrade to last release version 1.7.1, which resolves the bug. It auto updated before, and I did not notice.

ninok · 2022-02-02T20:59:35Z

Yes, forgot to mention that this is a regression that was introduced recently. It was working last week. I did not bisect when exactly it was introduced.
With this regression debugging is impossible for me so I will also downgrade.

ninok · 2022-02-02T21:02:48Z

Regarding duplicate variable names: In my case I have a pretty trivial function that has only some local vars with different names but it's still crashing.

calgagi · 2022-02-02T21:08:01Z

The problem is with some variable caching I did for supporting data breakpoints in MIEngine: microsoft/MIEngine#1257

I've got a fix working now. The Debug Adapter Protocol has a small issue where we only send the variable name and the stack frame it's associated with (or the parent variable if it's a child), so I'm just converting the cache's dictionaries to use TryAdd methods instead as a quick fix.

mdemoret-nv · 2022-02-02T21:11:06Z

@calgagi Do you know which version(s) this affects? Should we be downgrading to 1.7.1 or is there a pre-release version that should work?

Edit: Looks like its still an issue in pre-release 1.8.3

mdemoret-nv · 2022-02-02T21:14:15Z

One other thing I noticed: this seems to break removing breakpoints for me. Even after clicking in the source code to remove a breakpoint, gdb still stops at that line.

sean-mcmanus · 2022-02-02T21:23:19Z

@mdemoret-nv 1.8.3 is identical to 1.8.2. You should try our previous Insiders -- 1.8.1, which has older debugger binaries.

calgagi · 2022-02-02T21:25:05Z

Anytime we evaluate a variable more than once (in the same break state while debugging) or stop when there are 2 or more variables with the same name, the debugger will crash. The variable(s) must be in the same stack frame.

ruabmbua · 2022-02-04T11:20:13Z

Its funny, even calling -exec p <varname> will cause the issue. Was not aware that the debugger plugin also looks into the raw gdb commands.

aakash0641 · 2022-02-05T02:59:52Z

@WardenGnaw @WardenGnaw I switched C/C++ version to 1.8.1. and issue still persists. So I downgraded it further to 1.7.1 and issue still persists. Can you help please ?

aakash0641 · 2022-02-05T03:00:46Z

@WardenGnaw Providing output from Debug Console: (replying here as you closed #8776

RobertoMex · 2022-02-05T03:06:44Z

Switch to 1.7.1 close VSCode and re open VSCode. Just worked for me.

aakash0641 · 2022-02-05T03:07:38Z

@mdemoret-nv 1.8.3 is identical to 1.8.2. You should try our previous Insiders -- 1.8.1, which has older debugger binaries.

I tried downgrading C/C++ up till 1.7.1 and issue is still present. Hey, what is Insiders? Is it something different from C/C++ extension? I was getting popup messages in VSCode regarding installing insiders. I didn't downgrade Insiders specifically. I searched for it in list of installed extensions but could not locate it. Any help please?

aakash0641 · 2022-02-05T03:13:26Z

Switch to 1.7.1 close VSCode and re open VSCode. Just worked for me.

Didn't work for me. I even restarted my laptop to avoid any trace of running processes.

lipracer · 2022-02-05T14:04:46Z

After I update the vscode version to latest I get the same error.An item with the same key has already been added. Key:

aakash0641 · 2022-02-06T01:14:06Z

@WardenGnaw As in by Debug Console, there is no error shown, so it seems that the issue I am facing is not same as #8760 . In that case, I request you to re-open issue #8776 and help.

briaguya-ai · 2022-02-06T02:04:37Z

i am also running into this issue, i'll update this comment when the fix is released and I've tested it

edit: fixed for me in v1.8.5 Pre-Release

zeroxia · 2022-02-07T03:28:15Z

I got this error when debugging.

System: Ubuntu 18.04

VSCode version:

Version: 1.63.2
Commit: 899d46d82c4c95423fb7e10e68eba52050e30ba3
Date: 2021-12-15T09:39:46.686Z
Electron: 13.5.2
Chromium: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Linux x64 5.4.0-97-generic

C/C++ tools extension: v1.8.3 Pre-Release

Workspace is in a running docker container.

An rec error message in Debug console is shown:
Stopping due to fatal error: ArgumentException: An item with the same key has already been added. Key: (Microsoft.MIDebugEngine.AD7StackFrame, __func__)

Then the debug cannot continue. I have to click the stop button to end the session, other buttons (continue, stepping etc) do not work anymore.

KindHeartedTraveler · 2022-02-07T07:38:33Z

system: Ubuntu 20.04.1
vscode version: 1.64.0

I have the same problem when debug the OpenJdk source code. I can't delete breakpoints in vscode editor area. So i run the commands in the DEBUG CONSOLE then get this problem.

The old version, 1.8.1 or 1.7.1 version works well. Make sure disable auto update extensions.

PeacefulWhale · 2022-02-07T08:41:49Z

System: macOS Monterey: 12.1 (21C52)
VSCode Version: 1.64.0
C/C++ Extension Version: 1.8.2 Release Version

I ran into the same problem.

I wrote this small C code to see if I could narrow it down, and it turns out that it's happening with almost everything.

#include <stdlib.h>
#include <stdio.h>

typedef struct test
{
    int i;
    // struct test *next;
} test;

int main()
{
    test first;
    first.i = 0;

    struct second
    {
        int i;
    } second;
    second.i = 1;

    int third = 0;

    // BREAKPOINT HERE.

    return 0;
}

Debugging any of the values (first.i, second.i, third) returns the same error:

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. Key: (Microsoft.MIDebugEngine.AD7StackFrame, first)

I decided to see what would happen if I removed the first element, by commenting everything out.

This changed the error to:

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. Key: (Microsoft.MIDebugEngine.AD7StackFrame, second)

I then commented out the second, and called the third item again.

Which then changed the problem to:

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. Key: (Microsoft.MIDebugEngine.AD7StackFrame, second)

Even something as simple as:

int main()
{
    int third = 0;
    // BREAKPOINT HERE.
    return 0;
}

will cause the error.

I don't have the time to try to figure it out right now, so I'll just switch to the later version.

Hopefully I'll be able to come back and help with it. I'm sorry if this information isn't useful and just clutters up this page.

Here is everything from the debugger:

Warning: Debuggee TargetArchitecture not detected, assuming x86_64.
=thread-selected,id="1"
=library-unloaded,id="[/Users/mikecabatingan/Desktop/Programming/Misc/Temp/test.compiled]()",target-name="[/Users/MYNAME/Desktop/Programming/Misc/Temp/test.compiled]()",host-name="[/Users/MYNAME/Desktop/Programming/Misc/Temp/test.compiled]()"
Loaded '[/usr/lib/dyld]()'. Symbols loaded.
Loaded '[/Users/MYNAME/Desktop/Programming/Misc/Temp/test.compiled]()'. Symbols loaded.
Loaded '[/usr/lib/libSystem.B.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libcache.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libcommonCrypto.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libcompiler_rt.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libcopyfile.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libcorecrypto.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libdispatch.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libdyld.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libkeymgr.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libmacho.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libquarantine.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libremovefile.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_asl.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_blocks.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_c.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_collections.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_configuration.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_containermanager.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_coreservices.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_darwin.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_dnssd.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_featureflags.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_info.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_m.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_malloc.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_networkextension.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_notify.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_product_info_filter.dylib]()'. Cannot find or open the symbol file.
Loaded '[/usr/lib/system/libsystem_sandbox.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_secinit.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_kernel.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_platform.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_pthread.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_symptoms.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libsystem_trace.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libunwind.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/system/libxpc.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/libc]()++abi.dylib'. Symbols loaded.
Loaded '[/usr/lib/libobjc.A.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/liboah.dylib]()'. Symbols loaded.
Loaded '[/usr/lib/libc]()++.1.dylib'. Symbols loaded.
Execute debugger commands using "-exec <command>", for example "-exec info registers" will list registers in use (when GDB is the debugger)
third
0
Stopping due to fatal error: ArgumentException: An item with the same key has already been added. Key: (Microsoft.MIDebugEngine.AD7StackFrame, third)

Putting anything into the debugger (even if it's not "legal" and would return an error anyway) causes the same problem to occur, for example:

garbageIn
error: <user expression 0>:1:1: use of undeclared identifier 'garbageIn'
garbageIn
^
Stopping due to fatal error: ArgumentException: An item with the same key has already been added. Key: (Microsoft.MIDebugEngine.AD7StackFrame, third)

PeacefulWhale · 2022-02-07T17:49:17Z

I've confirmed that this issue still exists in 1.8.3

sean-mcmanus · 2022-02-07T19:08:47Z

@PeacefulWhale 1.8.3 is identical to 1.8.2 (VS Code is requiring that we release 2 identical versions of our extension in order to support the Pre-Release channel, see the discussion at microsoft/vscode#142040). The fix is expected to be in our 1.8.4/1.8.5 release later today.

PeacefulWhale · 2022-02-07T19:49:17Z

@sean-mcmanus

Ah, thank you, I wasn’t aware of the practice.

Thank you for your work!

lucasexe · 2022-02-08T01:16:03Z

I've also was been facing this issue but I've just checked the new release and the issue is gone!

Thanks for the quick fix :)

sean-mcmanus · 2022-02-08T16:14:45Z

Yes, it's fixed with https://github.com/microsoft/vscode-cpptools/releases/tag/1.8.4 (or 1.8.5, which is identical, except using that version will auto-update to 1.9.0 (insiders) when we release that).

perrog · 2022-02-10T14:27:48Z

My workaround has been to collapse the Variables view and prevent evaluation of variables while stepping. (If it happens again).

sean-mcmanus pinned this issue Feb 2, 2022

calgagi self-assigned this Feb 2, 2022

calgagi added the debugger label Feb 2, 2022

calgagi mentioned this issue Feb 2, 2022

Fix for duplicate variable names causing debugging crash microsoft/MIEngine#1271

Merged

sean-mcmanus added the regression A bug that didn't exist in a previous release label Feb 2, 2022

sean-mcmanus added this to the 1.8.4 milestone Feb 2, 2022

sean-mcmanus mentioned this issue Feb 3, 2022

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. #8768

Closed

calgagi mentioned this issue Feb 3, 2022

Support vaguely named variables in VariableManager's cache microsoft/MIEngine#1272

Merged

WardenGnaw mentioned this issue Feb 4, 2022

While debugging using VSCode, execution goes into infinite loop. #8776

Closed

WardenGnaw added the fixed Check the Milestone for the release in which the fix is or will be available. label Feb 4, 2022

briaguya-ai mentioned this issue Feb 6, 2022

If I pause with P and then go into the Retroarch menu with F1,the game is automatically unpaused and muted and if I press P again in that menu nothing happens libretro/RetroArch#11776

Closed

sean-mcmanus mentioned this issue Feb 7, 2022

Install Another Version action should show all versions for pre-release extension and only released versions for released extension version microsoft/vscode#142040

Closed

sean-mcmanus closed this as completed Feb 8, 2022

sean-mcmanus unpinned this issue Feb 8, 2022

obdopqo mentioned this issue Feb 9, 2022

I can't evaluate any valuable in the debug console. franneck94/Vscode-C-Cpp-Runner#56

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. #8760

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. #8760

ninok commented Feb 2, 2022

jmazar commented Feb 2, 2022

ruabmbua commented Feb 2, 2022 •

edited

Loading

ruabmbua commented Feb 2, 2022

markrussell-cpu commented Feb 2, 2022

ruabmbua commented Feb 2, 2022 •

edited

Loading

ninok commented Feb 2, 2022

ninok commented Feb 2, 2022

calgagi commented Feb 2, 2022

mdemoret-nv commented Feb 2, 2022 •

edited

Loading

mdemoret-nv commented Feb 2, 2022

sean-mcmanus commented Feb 2, 2022

calgagi commented Feb 2, 2022

ruabmbua commented Feb 4, 2022

aakash0641 commented Feb 5, 2022

aakash0641 commented Feb 5, 2022

RobertoMex commented Feb 5, 2022

aakash0641 commented Feb 5, 2022

aakash0641 commented Feb 5, 2022 •

edited

Loading

lipracer commented Feb 5, 2022

aakash0641 commented Feb 6, 2022

briaguya-ai commented Feb 6, 2022 •

edited

Loading

zeroxia commented Feb 7, 2022

KindHeartedTraveler commented Feb 7, 2022

PeacefulWhale commented Feb 7, 2022 •

edited

Loading

PeacefulWhale commented Feb 7, 2022

sean-mcmanus commented Feb 7, 2022

PeacefulWhale commented Feb 7, 2022

lucasexe commented Feb 8, 2022

sean-mcmanus commented Feb 8, 2022

perrog commented Feb 10, 2022 •

edited

Loading

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. #8760

Stopping due to fatal error: ArgumentException: An item with the same key has already been added. #8760

Comments

ninok commented Feb 2, 2022

jmazar commented Feb 2, 2022

ruabmbua commented Feb 2, 2022 • edited Loading

ruabmbua commented Feb 2, 2022

markrussell-cpu commented Feb 2, 2022

ruabmbua commented Feb 2, 2022 • edited Loading

ninok commented Feb 2, 2022

ninok commented Feb 2, 2022

calgagi commented Feb 2, 2022

mdemoret-nv commented Feb 2, 2022 • edited Loading

mdemoret-nv commented Feb 2, 2022

sean-mcmanus commented Feb 2, 2022

calgagi commented Feb 2, 2022

ruabmbua commented Feb 4, 2022

aakash0641 commented Feb 5, 2022

aakash0641 commented Feb 5, 2022

RobertoMex commented Feb 5, 2022

aakash0641 commented Feb 5, 2022

aakash0641 commented Feb 5, 2022 • edited Loading

lipracer commented Feb 5, 2022

aakash0641 commented Feb 6, 2022

briaguya-ai commented Feb 6, 2022 • edited Loading

zeroxia commented Feb 7, 2022

KindHeartedTraveler commented Feb 7, 2022

PeacefulWhale commented Feb 7, 2022 • edited Loading

PeacefulWhale commented Feb 7, 2022

sean-mcmanus commented Feb 7, 2022

PeacefulWhale commented Feb 7, 2022

lucasexe commented Feb 8, 2022

sean-mcmanus commented Feb 8, 2022

perrog commented Feb 10, 2022 • edited Loading

ruabmbua commented Feb 2, 2022 •

edited

Loading

ruabmbua commented Feb 2, 2022 •

edited

Loading

mdemoret-nv commented Feb 2, 2022 •

edited

Loading

aakash0641 commented Feb 5, 2022 •

edited

Loading

briaguya-ai commented Feb 6, 2022 •

edited

Loading

PeacefulWhale commented Feb 7, 2022 •

edited

Loading

perrog commented Feb 10, 2022 •

edited

Loading