Home/ Questions/Q 7078567
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T06:33:50+00:00

My monodroid application builds and runs fine, but breakpoints are not being hit. This

  • 0

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

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

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

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 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*

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

Thanks in advance for any insight.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    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.

    • 0