- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
CALL foo(array1+array2)
Is there a way to turn of this behavior and avoid having to step through chkstk.asm other than setting breakpoints in the subroutine foo or using the "Run to cursor" feature?
Thanks,
Jon
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Jon
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I don't know of anyway to tellthe VS debugger that you're not interested stepping intochkstk.asm. (That routine is called when the arguments to the subroutine you are interested in are being setup up, so when you stop at the line with the CALL, it's the next routine called.)
Other than what you mention, if you do get into chkstk.asm, SHIFT+F11 should return you to the calling program and another F11 should get you into the routine you're interested in.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
In the Property Pages for the Solution (not Project), Under Common Properties / Debug Source Files, I have listed all the .asm files I don't want debugged.
I haven't got this set for all my solutions I am working with, so I'm not sure how successful this is, as I still step into the .asm files occasionally. VERY ANOYING! We really want a fix. I first reported this about two years ago, I think.
David
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page