`gdb-oneapi` debug breakpoint doesn't work at all in VSCode

Summary

I can set breakpoints in VSCode. I can see the red dots. However, once I start debugging, the red dots move to other lines. Trying to set breakpoints during debugging is like catching the air! It just either doesn't stick at all or moves to other lines. I am using CMake and this is at the top of my CMakeLists.txt:

cmake_minimum_required(VERSION 3.30.3 FATAL_ERROR)

project(DataStructuresAlgorithms CXX)

set(CMAKE_CXX_STANDARD 26)
set(CMAKE_CXX_STANDARD_REQUIRED ON)

set(CMAKE_BUILD_TYPE "Debug")

# ###############################################################################
# Global compiler options
# https://stackoverflow.com/questions/79444534/vscode-cmake-configure-does-not-generate-cmakecache-txt-from-cmakelists-txt
# CMAKE_CXX_COMPILER_ID is set only at the project() call, when CMake actually detect compilers.
# ###############################################################################
if(MSVC)
    # remove default flags provided with CMake for MSVC
    set(CMAKE_CXX_FLAGS "")
    set(CMAKE_CXX_FLAGS_DEBUG "")
    set(CMAKE_CXX_FLAGS_RELEASE "")
elseif("${CMAKE_CXX_COMPILER_ID}" MATCHES "GNU")
    message("-- Setting GNU options from CMakeLists.txt")
    set(CMAKE_CXX_FLAGS "-std=gnu++26 -fdiagnostics-color=always" CACHE STRING "CXX build flags" FORCE)
    set(CMAKE_CXX_FLAGS_DEBUG "${CMAKE_CXX_FLAGS} -ggdb3 -Og -g3" CACHE STRING "Debug build flags" FORCE)
    set(CMAKE_CXX_FLAGS_RELEASE "${CMAKE_CXX_FLAGS} -O3 -DNDEBUG" CACHE STRING "Release build flags" FORCE)
endif()

Version

Report oneAPI Toolkit version and oneAPI Sample version or hash.

$ gdb-oneapi --version
GNU gdb (Intel(R) Distribution for GDB* 2025.3.0) 16.3
Copyright (C) 2025 Free Software Foundation, Inc.; (C) 2025 Intel Corp.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Environment

Ubuntu 25.10

Commencez par reproduire le comportement des points d’arrêt dans VSCode avec gdb-oneapi 16.3 sur Ubuntu 25.10, en utilisant la configuration de CMakeLists.txt présentée dans le rapport. Comparez les points d’arrêt définis avant et pendant le débogage, et vérifiez qu’ils restent sur les lignes sources prévues. Le travail est considéré comme terminé lorsque la cause a été identifiée et qu’une correction du déplacement et de l’échec des points d’arrêt a été documentée ou validée.