C++ developers lack a smooth, trustworthy debugging setup
C++ developers report friction both while debugging—repetitive stepping and breakpoint work, or relying on logging instead of inspecting values—and while choosing an IDE they trust. Their current approaches include manual debugging workarounds and asking communities for recommendations. The signals point to a shared C++ development-environment problem, but not to one proven, dominant feature request.
For C++ developers setting up and debugging projects. Mentioned from Mar 2021 to May 2026 on Bluesky, GitHub and Stack Exchange.
4 different people described this problem in 3 separate discussions.
- Indie fit
- 3.0/10
- Pain
- 5.0/10
- Frequency
- 5.8/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- High
- Build difficulty
- High
What people said
Quoted word for word. Follow a link to read the whole discussion.
Yeah, that workaround may work sometimes, but such workaround is a productivity killer like @cdacamar mentioned already. Let's consider a test code below:
That is, during the development process, I want to make changes to the code, run it and immediately see the values of all variables obtained as calculation results, without using logging procedures, etc
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 3 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks