-
Products and Technology
By Category
-
Groups
Activity Groups
Industry Groups
Influence and Feedback Groups
Interest Groups
Location Groups
Customer Only Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
Learning and Support
-
- Products and Technology
- Groups
- Developers
- Partners
- Events
- Help Center
- Topic Pages
-
Explore SAP
- Explore SAP
-
Products
- Products
- Autonomous Enterprise
- Artificial intelligence
- Data and analytics
- Autonomous Suite
- Technology platform
- Transformation management
- Midsize business solutions
- Financial management
- Spend management
- Supply chain management
- Human capital management
- Customer experience
- Enterprise resource planning
- Business network
- Sustainability management
- SAP Store
- Try SAP
- View all industries
- Partners
- Services
- Learning and Support
- About
- SAP Community
- Developers
- ABAP
- Forum
- Re: Debug command "Suspend" in Eclipse ADT
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- SAP Managed Tags
- ABAP Development
I'm wondering what the debug command "Suspend" is for, when it can be selected, when to use it. Each time I look at the button, it's inactive.
NB:
- The command "Suspend" didn't exist in the "old/new" SAP GUI backend debugger.
- I couldn't find any explanation in the SAP Help Portal: https://help.sap.com/docs/abap-cloud/abap-development-tools-user-guide/navigating-in-debugger?utm_so...
Thank you.
Sandra
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- SAP Managed Tags
- ABAP Development
The command "Suspend" can be selected in the Eclipse ADT debugger when the debugger is "stepping", i.e. when the debugger has been started (i.e. it has stopped on a first break point) and the code is currently running (i.e. when continuing after a break point and before the next break point, if any).
The command "Suspend" suspends the execution as soon as possible (technical limitations like SQL running, minimal amount of time), anywhere in the code.
One reason to use it is when the code runs for a long time without pausing at one of your breakpoints, and you suspect a performance issue or an endless loop.
One frequent case is that a background job is running for a long time and has to be debugged for analyzing:
- Start SM51 via Eclipse ADT, select the workprocess and then the menu Process > Program > Debug
- The debugger starts anywhere in the code
- You can then check what happens, add breakpoints to better analyze
- If you continue the job and your breakpoints are still not reached, you may run the command "Suspend" to suspend the execution and start debugging.
Remarks about the "old/new" SAP GUI backend debugger:
- The command equivalent to "Suspend" was quite exhausting: SM51 > Select the workprocess > menu Process > Program > Debug, and often did not work the second and next times (no idea why, maybe one workaround was to continue the execution by stopping the backend debugger via the menu Debugger > Exit (Application continues running)).
- "Suspend" was missing because, if I'm not wrong, it was technically impossible because only one process could be active at a moment, either the debugged process or the debuggee process, i.e. when the debugged process was running it was not possible to click a debug option in the debuggee process as its SAP GUI window was inactive.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
- SAP Managed Tags
- ABAP Development
The command "Suspend" can be selected in the Eclipse ADT debugger when the debugger is "stepping", i.e. when the debugger has been started (i.e. it has stopped on a first break point) and the code is currently running (i.e. when continuing after a break point and before the next break point, if any).
The command "Suspend" suspends the execution as soon as possible (technical limitations like SQL running, minimal amount of time), anywhere in the code.
One reason to use it is when the code runs for a long time without pausing at one of your breakpoints, and you suspect a performance issue or an endless loop.
One frequent case is that a background job is running for a long time and has to be debugged for analyzing:
- Start SM51 via Eclipse ADT, select the workprocess and then the menu Process > Program > Debug
- The debugger starts anywhere in the code
- You can then check what happens, add breakpoints to better analyze
- If you continue the job and your breakpoints are still not reached, you may run the command "Suspend" to suspend the execution and start debugging.
Remarks about the "old/new" SAP GUI backend debugger:
- The command equivalent to "Suspend" was quite exhausting: SM51 > Select the workprocess > menu Process > Program > Debug, and often did not work the second and next times (no idea why, maybe one workaround was to continue the execution by stopping the backend debugger via the menu Debugger > Exit (Application continues running)).
- "Suspend" was missing because, if I'm not wrong, it was technically impossible because only one process could be active at a moment, either the debugged process or the debuggee process, i.e. when the debugged process was running it was not possible to click a debug option in the debuggee process as its SAP GUI window was inactive.
Bluesky