VS2017 C ++调试器问题 [英] VS2017 C++ debugger issues

查看:229
本文介绍了VS2017 C ++调试器问题的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在将本地MFC C ++项目从VS2015移植到vS2017,并且发现调试过程不稳定。 首先,如果我在程序运行时调试并继续启用编辑并继续启用某些源的更改,
并选择调试/应用代码更改,它会将更改报告为已生成但实际上并未更改功能或者让我应用一个新的断点,直到我停止调试并进行重建。 如果我先打破所有,它大部分时间都可以正常工作。 
其次,线程优先级栏去了哪里? 线程窗口在VS2015中看起来像这样;

I'm in the process of porting a native MFC C++ project from VS2015 to vS2017 and am finding the debugging process less stable.  Firstly, if I make a change to some source with Edit and Continue enabled while debugging while the program is running, and select Debug / Apply code changes, it reports the change as being made but doesn't actually change the functionality or let me apply a new breakpoint until I stop debugging and do a rebuild.  If I break all first, it works ok most of the time.  Secondly, where has the thread priority column gone?  The thread window looked like this in VS2015;

在VS2017中它现在看起来像这样

像许多现代程序一样,我使用线程池,其中非活动线程较低。优先 无法按优先级排序会使线程窗口很难使用。 我计划将2017年作为我的主要开发平台迁移到2017年,但目前感觉就像从VS2015逆行一步。

Like many modern programs, I work with a thread pool, where inactive threads have lower priority.  Not being able sort by priority makes the thread window very difficult to use.  I had planned on migrating to 2017 as a my main development platform, but currently it feels like a retrograde step from VS2015.

推荐答案

要显示优先级列,请从列中选择
list。

In order to show the Priority column, select it from the Columnslist.


这篇关于VS2017 C ++调试器问题的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆