vs codium, c++, debugger shows assembler instructions instead of c++ instructions like visual studio community

[sgorgiSW]

Hello,
I am trying to debug a c++ program in vs codium with the lldb extension, but when I run to debug the code, it shows assembly instructions instead of the cpp files and commands on "c++ level". I compiled the code with GCC 12.3.0 with the debug setting. My source files are in the "src" directory, header files are in "include" and the resulting compiled program in "build/src". When I start the debugging, it does say source unknown above the assembly instructions, maybe that is why the debugger doesn't show c++ instructions? The instructions right after pressing debug are:

; Symbol: _start
; Source: unknown
7FFFF7FE32F0: 48 89 E7                   movq   %rsp, %rdi
7FFFF7FE32F3: E8 98 0D 00 00             callq  0x7ffff7fe4090  ; _dl_start at rtld.c:527:1

This is my launch.json file:

{
   "version": "0.2.0",
   "configurations": [
       {
           "type": "lldb",
           "request": "launch",
           "name": "Debug",
           "program": "${workspaceFolder}/src/2DHE-solver",
           "stopOnEntry": true,
           "args": [],
           "cwd": "${workspaceFolder}"
       }
   ]
}

Does anybody know, how I could make the debugger process instructions on "c++ level"? I don't know assembly and the code is long, so I don't think I will be able to debug the code in assembly. And if I put it into visual studio community (where I could debug it in c++ instructions), it doesn't even do the bug (segfault), like it does when compiling it with GCC.

I found something similar in this thread #251, but my debugger shows assembly instructions right away, so I thought I would ask, maybe I made some silly mistake or something.

[vadimcn]

Remove "stopOnEntry": true. This instructs the debugger to stop in early startup code, way before the main() is called.

[sgorgiSW]

Thank you very much, I can finally debug my code =D. I remember that it showed assembly instructions even before I wrote the stop on entry, so I didn't realize that could be the problem, but I must have remembered that wrong and debugged the code with "stopOnEntrx" from the start, appologies for my basic mistake. Thank you!