为什么 Visual Studio 会跳过 ThreadPool 工作项中的异常？

发布于 2024-07-18 08:06:18 字数 1648 浏览 8 评论 0原文

我知道另一篇帖子，但它没有似乎适用于我的情况。

首先，这是我的环境：
Windows XP 64 位 SP3； Visual Studio 2008 带 SP； .NET 3.5 SP1； WPF 应用程序。

我的问题是我似乎无法走到异常发生的地方。它只是继续运行而不是继续调试会话。

这是一些代码——我没有编写全部代码，所以请不要对命名进行注释:)

// start up the WPF application
// set the handler for the Checked event
ToggleButton channelButton1 = new ToggleButton();
channelButton1.Checked += (s, e) => 
     ThreadPool.QueueUserWorkItem(SetTcpChannel, 1);

然后在 SetTcpChannel 方法中：

    try
    {
        int channel = (int)state;
        EnsureTcpSocket();
        // more logic to do stuff with channel 
        // that we don't care about for SO
        ...
    }
    catch (Exception e)
    {
        // just for illustration
        // this is where I expected the code to return
        ...
    }

最后，在异常实际发生的地方（在EnsureTcpSocket内）：

    if (_tcp == null)
    {
        // this is not a valid ip/port since the 
        // target machine is not running (test condition)
        // but that's ok, I should get some exception 
        // and continue debugging...right?
        _tcp = new TcpClient(ip, port);
    }

这是我一直在做的事情：

我在里面的 EnsureTcpSocket 行 SetTcpChannel、
F11（步入）EnsureTcpSocket 所以我可以看到 _tcp 部分代码
尝试按 F10（步进） TcpClient 构造函数

在最后一步，应用程序从调试器中恢复并继续运行，我从未看到任何异常。

有任何想法吗？

原文

I am aware of this other post, but it doesn't seem to apply to my situation.

First off, here is my environment:
Windows XP 64-bit SP3; Visual Studio 2008 w/ SP; .NET 3.5 SP1; WPF application.

My problem is that I cannot seem to step to where my exception happens. It just keeps running instead of continuing the debugging session.

Here is some code -- I didn't write all of it, so please, no need for comments on naming :)

// start up the WPF application
// set the handler for the Checked event
ToggleButton channelButton1 = new ToggleButton();
channelButton1.Checked += (s, e) => 
     ThreadPool.QueueUserWorkItem(SetTcpChannel, 1);

Then in that SetTcpChannel method:

    try
    {
        int channel = (int)state;
        EnsureTcpSocket();
        // more logic to do stuff with channel 
        // that we don't care about for SO
        ...
    }
    catch (Exception e)
    {
        // just for illustration
        // this is where I expected the code to return
        ...
    }

And finally, in the place where the exception actually happens (inside EnsureTcpSocket):

    if (_tcp == null)
    {
        // this is not a valid ip/port since the 
        // target machine is not running (test condition)
        // but that's ok, I should get some exception 
        // and continue debugging...right?
        _tcp = new TcpClient(ip, port);
    }

Here is what I have been doing: