Tries to set breakpoint at main, although setting stopAtEntry is False

[fr43nk]

Hi,

I use the c_cpp extension in VScode with a large c++ project.
One issue is, that starting the debugger session takes more than one minute.
I activated the logging to see what is happening. It came out, that there is a log entry saying:

1: (7051) <-1009-break-insert -f main

Then the log prints all methods within my project with the name main.
Finally the log contains the time it took to search all those methods:

--> E (output): {"type":"event","event":"output","body":{"category":"console","output":"1: (47494) 1009: elapsed time 40443\n"},"seq":112}

The thing about this: I disabled the stopAtEntry in the launch settings of my project

{
"name": "(GDB) mybinary (logging)",
"type": "cppdbg",
"program": "/path/to/mybinary.exe",
"request": "launch",
"cwd": "/path/to",
"stopAtEntry": false,
"linux": {},
"MIMode": "gdb",
"miDebuggerPath": "/u1/debugger/gdb-13.2.0/bin/gdb",
"logging": {
  "engineLogging": true,
  "moduleLoad": true,
  "trace": true,
  "traceResponse": true,
}

I think that this is an error not using the setting.

Looking at the source code, there might be a something wrong in:

MIEngine\src\MIDebugEngine\Engine.Impl\DebuggedProcess.cs:821

Best regards,
Frank

[fr43nk]

Is there anyone who can acknowledge this issue?

[oold]

We customize the Debug Engine since it tries to run too many expensive commands on the debugger, which causes e.g. one minute or more of time between entering break mode and actually being able to do anything in the IDE for our platform, so I've seen a lot of the code.

The main breakpoint is set because the Debug Engine needs to emit an "entrypoint hit" event. IDK why exactly it needs to emit the event, but I remember things not working quite right if the event is removed. In VS, there is a thread-safe wrapper around the engine callback, but that doesn't really matter here. The engine callback gets hit for VS and VS Code.

Entrypoint event:

MIEngine/src/MIDebugEngine/Engine.Impl/EngineCallback.cs

Line 155 in 4aef1f4

public void OnEntryPoint(DebuggedThread thread)

Event callback for VS:

MIEngine/src/DebugEngineHost/VSImpl/VSEventCallbackWrapper.cs

Line 73 in 4aef1f4

int IDebugEventCallback2.Event(IDebugEngine2 engine, IDebugProcess2 process, IDebugProgram2 program, IDebugThread2 thread, IDebugEvent2 @event, ref Guid riidEvent, uint attribs)

Event handler for the debug session:

MIEngine/src/OpenDebugAD7/AD7DebugSession.cs

Line 3465 in 4aef1f4

public void HandleIDebugEntryPointEvent2(IDebugEngine2 pEngine, IDebugProcess2 pProcess, IDebugProgram2 pProgram, IDebugThread2 pThread, IDebugEvent2 pEvent)

I'd also like to see a comment from the maintainers on why exactly this is done.