Bug 10809 - Debugger not stopping (breakpoint) at bottom of stack
Summary: Debugger not stopping (breakpoint) at bottom of stack
Status: RESOLVED NORESPONSE
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 4.0
Hardware: PC Linux
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2013-03-01 08:12 UTC by Matt
Modified: 2013-12-05 18:34 UTC (History)
1 user (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 Matt 2013-03-01 08:12:51 UTC
Description of Problem:

When debugger stops at a break point the editor displays a point a level above the breakpoint in the call stack. 

Steps to reproduce the problem:
1. Place a breakpoint. 
2. Run program.
3. Debugger stops at breakpoint.
4. Editor is displaying a point in the call stack above the last frame of the call stack (the last frame is correctly where the breakpoint is).


Actual Results:

Breaking above bottom level of the call stack.

Expected Results:

Breaking at the bottom level of the call stack.

How often does this happen? 

Always with the project I am working on.

Additional Information:

Here is a stack trace reflecting the stack when stopped at the breakpoint (numbers added for clarity):

[0] LightStation.Storage.Temporal.HdfFile.LoadStringVector (path="/vec") in /home/calder/Work/Lightkeeper/lightstation/store/src/csharp/LightStation.Storage.Temporal/HdfFile.cs:999
[1] LightStation.Storage.Temporal.Tests.HdfFileTests.TestStringVector () in /home/calder/Work/Lightkeeper/lightstation/store/src/csharp/LightStation.Storage.Temporal.Tests/HdfFileTests.cs:376
[2] NUnit.Core.Reflect.InvokeMethod (method={Void TestStringVector()}, fixture={LightStation.Storage.Temporal.Tests.HdfFileTests}, args=(null)) in 
[3]NUnit.Core.TestMethod.RunTestMethod (testResult={NUnit.Core.TestResult}) in 
[4] NUnit.Core.TestMethod.RunTestCase (testResult={NUnit.Core.TestResult}) in 
[...] Edited

The breakpoint is in the file referred to in line [0], but the editor is displaying the file in line [1]. The editor is at the right place in the file, as if the Call Stack entry had been clicked.
Comment 1 Jeffrey Stedfast 2013-03-05 16:55:25 UTC
The reason for this is because frame 0 is in library code and either:

1. the library project is not part of your solution

or

2. you have "Debug project code only" enabled in the debugger preferences


Does that fix it for you?
Comment 2 Mikayla Hutchinson [MSFT] 2013-03-05 21:55:07 UTC
It would be AND not OR.

"Debug project code only" means it only steps into the code of assemblies produced by projects in the solution.
Comment 3 Matt 2013-03-06 06:25:20 UTC
No the code is definitely in the project. I believe it is related to tests, stack [0] in the example is code being tested, and stack [1] is an (Nunit if it matters) test. Nevertheless I unchecked the "Debug project code only" and will keep an eye on it. 

Matt
Comment 4 PJ 2013-11-19 17:04:20 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 5 PJ 2013-12-05 18:34:21 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.