microsoft / microsoft/vscode-cpptools

Breakpoint's is not triggered while debugging the gameserver plugin

Open
#2,383 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

debugger
Dominant language
TypeScript
Stars
6.2k
Forks
1.7k
Avg merge
14h 46m
Merged PRs (30d)
61

Description

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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the breakpoint behavior with the evol-all project and compare VS Code debugging with gdbtui. Inspect the symlinked server-plugin path and the duplicate atcommand.c locations described in the report. Done means breakpoints in the plugin source bind and pause at the expected file rather than the server module.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cpp
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.