Bug 12069 - Cant debug class library
Summary: Cant debug class library
Status: RESOLVED NORESPONSE
Alias: None
Product: iOS
Classification: Xamarin
Component: Debugger ()
Version: 6.2.x
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2013-05-02 04:54 UTC by Amanda
Modified: 2013-12-05 18:34 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NORESPONSE

Description Amanda 2013-05-02 04:54:04 UTC
Hi 

I am on Xcode 4.6.2 (2067.2), Xamarin Studio Version 4.0.4 (build 2), and Xamarin.iOS Version: 6.2.4.2 (Business Edition).

I was able to hit breakpoints, and step into methods that are in class libraries. Recently, I stopped being able to do that in certain libraries. I have compared the project options to other libraries that I can step into, but I cant see any difference. This only happens when debugging to the iPad device. When debugging to the simulator I can step into the methods. Unfortunately I really want to debug to the iPad as I am troubleshooting code that prints to a bluetooth printer - cant use the simulator for this

Any ideas?

Thanks and Regards

Amanda
Comment 1 Rolf Bjarne Kvinge [MSFT] 2013-05-02 06:01:51 UTC
Can you try adding --debug:all to the additional mtouch arguments in the project's iOS Build options?
Comment 2 Amanda 2013-05-02 06:47:43 UTC
Hi Rolf

Thanks , however, adding -debug:all to the additional arguments of the Build /Compiler section of the Project Options did not make any difference.

Regards

Amanda
Comment 3 Rolf Bjarne Kvinge [MSFT] 2013-05-02 07:16:57 UTC
You need to add it to the "Additional mtouch arguments" of the "iOS Build" section.
Comment 4 Amanda 2013-05-02 08:06:13 UTC
Hi Rolf

The project in my solution where I cannot hit breakpoints, and cannot step into,  has a compile target of "Library". As it has this type of compile target, there is no iOS Build section in the Project Options.

I am able to hit break points in the project that has a Compile Target = Executable. This is the project that has the option "iOS Build".  However, I added the -debug:all to these arguments and it also didnt make a diffefrence.

Thanks for your help

Amanda
Comment 5 Rolf Bjarne Kvinge [MSFT] 2013-05-06 04:27:20 UTC
Can you reproduce the same problem if you try to create a similar solution from a template?

It not the problem is something related to the specific project you're working on, and we'd need access to that project in order to reproduce it (and fix it).
Comment 6 PJ 2013-11-19 17:04:08 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 7 PJ 2013-12-05 18:34:10 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.