断点未命中 Mono For Android (Monodroid) [英] Breakpoints not being hit Mono For Android (Monodroid)

问题描述

我的 monodroid 应用程序构建并运行良好，但未命中断点.这既适用于物理设备，也适用于模拟器.

My monodroid application builds and runs fine, but breakpoints are not being hit. This is both for physical devices and the emulator.

我创建了一个新的默认 Monodroid 应用程序，它确实遇到了断点.

I created a new default monodroid application and it does hit break points.

我尝试过重建、重新启动 ADB 和重新启动.我正在运行 VS2010，M4A 版本 4.0.1.

I have tried rebuilding, restarting ADB, and rebooting. I am running VS2010, M4A version 4.0.1.

Android 设备日志记录屏幕提供以下信息(包括 3 个调试会话)眼睛友好的版本MonoDroid-Debugger Specific.编辑按要求完整日志完整日志

The android device logging screen gives the following (this covers 3 debug sessions) Eye friendly version MonoDroid-Debugger Specific. EDIT Entire log as requested Full Log

*8:55 AM W 2477 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0i:8907,server=y,embedding=18:55 AM W 2477 MonoDroid-Debugger 接受标准输出连接:36上午 9:19 W 2738 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transport=dt_socketjoglevel=0,address=127.0.01:8913,server=y,embedding=1上午 9:19 W 2738 MonoDroid-Debugger 接受标准输出连接:36上午 9:27 W 2803 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transport=dt_socketjoglevel=0,address=127.0.Oi:8915,server=y,embedding=1上午 9:27 W 2803 MonoDroid-Debugger 接受标准输出连接:369:27 AM W 2838 MonoDroid-Debugger 未启动调试器，因为已达到超时值；当前时间:1326468477 超时 1326468463上午 9:29 W 2878 MonoDroid-Debugger 未启动调试器，因为已达到超时值；当前时间:1326468544 超时 1326468463上午 9:29 W 2896 MonoDroid-Debugger 未启动调试器，因为已达到超时值；当前时间:1326468544 超时 1326468463上午 9:29 W 2923 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transport=dt_socketjoglevel=0,address=127.0.01:8901,server=y,embedding=1上午 9:29 W 2923 MonoDroid-Debugger 接受标准输出连接:36上午 9:29 W 2959 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transport=dt_socketloglevel=0,address=12700.1:8901,server=y,embedding=1上午 9:29 W 2959 MonoDroid-Debuqqer 接受标准输出连接:-19:29 AM W 2982 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transpoft=dt_socketjoglevel=0,address=127.0.0i:8903,sen'er=y,embedding=l上午 9:29 W 2982 MonoDroid-Debugger 接受标准输出连接:37上午 9:30 W 3038 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8963,server=y,embedding=1上午 9:30 W 3038 MonoDroid-Debugger 接受标准输出连接:36上午 9:32 W 3071 MonoDroid-Debugger 未启动调试器，因为已达到超时值；当前时间:1326468730 超时:1326468676上午 9:32 W 3113 MonoDroid-Debugger 尝试使用以下选项初始化调试器:--debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8965,server=y,embedding=1上午 9:32 W 3113 MonoDroid-Debugger 接受标准输出连接:37*

*8:55 AM W 2477 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0i:8907,server=y,embedding=1 8:55 AM W 2477 MonoDroid-Debugger Accepted stdout connection: 36 9:19 AM W 2738 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transport=dt_socketjoglevel=0,address=127.0.01:8913,server=y,embedding=1 9:19 AM W 2738 MonoDroid-Debugger Accepted stdout connection: 36 9:27 AM W 2803 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transport=dt_socketjoglevel=0,address=127.0.Oi:8915,server=y,embedding=1 9:27 AM W 2803 MonoDroid-Debugger Accepted stdout connection: 36 9:27 AM W 2838 MonoDroid-Debugger Not starting the debugger as the timeout value has been reached; current-time: 1326468477 timeout 1326468463 9:29 AM W 2878 MonoDroid-Debugger Not starting the debugger as the timeout value has been reached; current-time: 1326468544 timeout 1326468463 9:29 AM W 2896 MonoDroid-Debugger Not starting the debugger as the timeout value has been reached; current-time: 1326468544 timeout 1326468463 9:29 AM W 2923 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transport=dt_socketjoglevel=0,address=127.0.01:8901,server=y,embedding=1 9:29 AM W 2923 MonoDroid-Debugger Accepted stdout connection: 36 9:29 AM W 2959 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transport=dt_socketloglevel=0,address=12700.1:8901,server=y,embedding=1 9:29 AM W 2959 MonoDroid-Debuqqer Accepted stdout connection: -1 9:29 AM W 2982 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transpoft=dt_socketjoglevel=0,address=127.0.0i:8903,sen’er=y,embedding=l 9:29 AM W 2982 MonoDroid-Debugger Accepted stdout connection: 37 9:30 AM W 3038 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8963,server=y,embedding=1 9:30 AM W 3038 MonoDroid-Debugger Accepted stdout connection: 36 9:32 AM W 3071 MonoDroid-Debugger Not starting the debugger as the timeout value has been reached; current-time: 1326468730 timeout: 1326468676 9:32 AM W 3113 MonoDroid-Debugger Trying to initialize the debugger with options: --debugger-agent=transport=dt_socket,loglevel=0,address=127.0.0.1:8965,server=y,embedding=1 9:32 AM W 3113 MonoDroid-Debugger Accepted stdout connection: 37*

遵循此处的建议我查看了 apk 的内部，确实看到了 .mdb 文件.

Following the advice given here I took a look inside the apk and I do see .mdb files.

提前感谢您提供任何见解.

Thanks in advance for any insight.

推荐答案

我安装了 Mono for Android 4.0.3，一切恢复正常.这并不能真正确定是什么损坏了……但我会忍受它.感谢您对 jpobst 的帮助.

I installed Mono for Android 4.0.3 and everything is back to normal. This doesn't really pin down what was broken... but I'll live with it. Thanks for your help jpobst.

这篇关于断点未命中 Mono For Android (Monodroid)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！