mirrors/eiffel-org
1
0
Fork 0
mirror of https://github.com/EiffelSoftware/eiffel-org.git synced 2025-12-07 07:12:25 +01:00
Code Issues Packages Projects Releases Wiki Activity

Author:jfiat

Browse Source 
Date:2011-10-06T12:35:46.000000Z


git-svn-id: https://svn.eiffel.com/eiffel-org/trunk@985 abb3cda0-5349-4a8f-a601-0c33ac3a8c38
This commit is contained in:
halw
2011-10-06 13:25:37 +00:00
parent 9121e2f9fd
commit 0beff24ee2
1 changed files with 41 additions and 40 deletions
Download Patch File Download Diff File Expand all files Collapse all files

81
documentation/current/eiffelstudio/eiffelstudio-reference/debugger/command-line-debugger.wiki
View File

@@ -6,20 +6,21 @@ The command line debugger is not as rich as the EiffelStudio debugger, however i
= How to enter the command line interface ? =
* ec -config your_system.ecf -debug
* Then you get the debug menu
--< Debugger main menu >--
(A) Set arguments
(E) Set environment
(D) Set working directory
(I) Display parameters
---
(R) Start and stop at breakpoints
(L) Start without stopping at breakpoints
(S) Step into
---
(H) Help
(Q) Quit
->
* Enter your choice using the letter inside parenthesis
--< Debugger main menu >--
(A) Set arguments
(E) Set environment
(D) Set working directory
(I) Display parameters
---
(R) Start and stop at breakpoints
(L) Start without stopping at breakpoints
(S) Step into
---
(H) Help
(Q) Quit
->
* Enter your choice using the letter inside parentheses
** (A) to set the arguments for the execution
** (E) to set the environment variables
** (D) for the working directory
@@ -27,36 +28,36 @@ The command line debugger is not as rich as the EiffelStudio debugger, however i
** When the execution is paused, you can display the menu by pressing ENTER
= To set breakpoints =
If you want to set breakpoints, you first need to step into (S) to start execution
** The execution starts and paused at the entry of the system
If you want to set breakpoints, you first need to step into (S) to start execution
** The execution starts, then pauses at the entry of the system
** Press ENTER to get the new "Debugger execution menu"
--< Debugger execution menu >--
(N) Step next
(I) Step into
(O) Step out
(C) Run to next stop point
(G) Run without stop point
(T) Toggle 'Ignore stop point'
(K) Kill application
(P) Pause application
---
(B) Breakpoints control
(D) Display information
(H) Help
->
--< Debugger execution menu >--
(N) Step next
(I) Step into
(O) Step out
(C) Run to next stop point
(G) Run without stop point
(T) Toggle 'Ignore stop point'
(K) Kill application
(P) Pause application
---
(B) Breakpoints control
(D) Display information
(H) Help
->
** Then you choose "(B) Breakpoints control" to add, modify or list breakpoints.
--< Debugger menu :: Breakpoints >--
(A) Add breakpoint
(M) Modify existing breakpoint
(L) List breakpoints
(H) Help
(..) Back to parent menu
->
--< Debugger menu :: Breakpoints >--
(A) Add breakpoint
(M) Modify existing breakpoint
(L) List breakpoints
(H) Help
(..) Back to parent menu
->
= Limitations =
* You can not interrupt the execution
* The command line debugger is not as rich as the EiffelStudio graphical debugger, and then you might miss specific functionalities (such as conditional breakpoints, ...)
* It is experimental, and would need more enhancement to answer advanced need, however it provides a simple (and limited) debugging facilities.
* It is not possible to interrupt the execution.
* The command line debugger is not as rich as the EiffelStudio graphical debugger. As a result you may miss specific functionalities (such as conditional breakpoints, ...) available in the EiffelStudio debugger.
* The command line debugger is experimental. It would need more enhancement to satisfy advanced debugging needs, however it provides simple (and limited) debugging facilities directly from the command line.