Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 305 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Debug Tip on Call Stack
ara3n
Member Posts: 9,256
Some people may not know this. So I suggested adding it in here.
When you are debugging, you see the call stack, usually at the bottom of the screen. You can double click on second or third line and debug window will point to the code on where it was called from so you can see all the from the begging of the call stack and how it got there.
This makes it easy to find out why the function or CU was called.
So the trick is to double click on other lines in the call stack to see the code.
When you are debugging, you see the call stack, usually at the bottom of the screen. You can double click on second or third line and debug window will point to the code on where it was called from so you can see all the from the begging of the call stack and how it got there.
This makes it easy to find out why the function or CU was called.
So the trick is to double click on other lines in the call stack to see the code.
0
Comments
http://plataan.typepad.com/microsoftdyn ... -116460644
Independent Consultant/Developer
blog: https://dynamicsuser.net/nav/b/ara3n