Breakpoint's is not triggered while debugging the gameserver plugin

Type: Debugger

• OS and Version: Ubuntu 16.04
• VS Code Version: 1.25.1
• C/C++ Extension Version: 0.17.7
• Other extensions you installed (and if the issue persists after disabling them): C++ Intellisense, CMake, CMake Tools (I have much more, not sure this would be a good idea to place all of them).

Can not debug plug-in for game server using visual studio code. Server is build with gcc, project is located at https://gitlab.com/evol/evol-all. I can debug server itself, but can not debug plug-in.

To Reproduce
Steps to reproduce the behavior:

1. Build the server and plugin
2. Setup breakpoints in the server code and plug-in code
3. Run the server
4. Trigger actions
5. Debugger is paused at server code breakpoints, but not at plug-in’s breakpoints.

I think that may be connected with symlinks, coz plug-in folder is symbolic linked with another location. For example, i have project placed in /home/acsvln/development/evol folder. Plug-in is located in /home/acsvln/development/evol/server-code/src/evol folder. Folder with path /home/acsvln/development/evol/server-plugin is symlinked with /home/acsvln/development/evol/server-code/src/evol.
While debugging plug-in, debugger is paused at server code module with same name. I try to debug:
/home/acsvln/development/evol/server-code/src/evol/src/emap/atcommand.c
but i have pause at
/home/acsvln/development/evol/server-code/src/map/atcommand.c.
Same module names may be problem too.
Moreover, when i set breakpoints in the plug-in source code, i can not set them in some locations, where usually breakpoints can be set.
Technically, i can debug plugin with gdbtui, so problem is connected with either visual studio code, either c++ plugin.

Comienza reproduciendo el comportamiento de los puntos de interrupción con el proyecto evol-all y compara la depuración de VS Code con gdbtui. Inspecciona la ruta enlazada simbólicamente de server-plugin y las ubicaciones duplicadas de atcommand.c descritas en el informe. Se considera terminado cuando los puntos de interrupción del código fuente del plugin se vinculan y la ejecución se pausa en el archivo esperado en lugar de en el módulo del servidor.