Difference between revisions of "Debugger Console App"
("Terminal" seems to be "Terminal Output" on Laz trunk anyway) |
("app" currently is the term mostly used for mobile applications. Therefore replaced by "application" as it's more general and accurate.) |
||
Line 7: | Line 7: | ||
== Windows == | == Windows == | ||
− | On Windows, the | + | On Windows, the application will open its own console window, just as it would outside the debugger. There is no need to do anything special. |
== Linux == | == Linux == | ||
Line 21: | Line 21: | ||
It shows the raw output of your application. Note it has no support for any escape sequences, as some terminals may have. | It shows the raw output of your application. Note it has no support for any escape sequences, as some terminals may have. | ||
− | Anything you type into this window will be sent to your | + | Anything you type into this window will be sent to your application. |
== Mac == | == Mac == | ||
Line 27: | Line 27: | ||
Unfortunately there is currently no built-in support for debugging console applications. | Unfortunately there is currently no built-in support for debugging console applications. | ||
− | Console | + | Console applications do not have their own terminal, but use the terminal they were started from (the terminal of the shell they were started from). |
− | When started from within Lazarus, there is no such terminal. You can specify a "starter application" (like xterm) under menu "Run" => "Run parameters". however this only works if you start your | + | When started from within Lazarus, there is no such terminal. You can specify a "starter application" (like xterm) under menu "Run" => "Run parameters". however this only works if you start your application without a debugger. '''This does not work for debugging.''' |
There are a couple of workarounds. | There are a couple of workarounds. | ||
Line 44: | Line 44: | ||
Open a terminal outside of Lazarus and run | Open a terminal outside of Lazarus and run | ||
− | + | <syntaxhighlight lang="bash> | |
+ | pty | ||
+ | </syntaxhighlight> | ||
It should return something like | It should return something like | ||
/dev/pty/2 | /dev/pty/2 | ||
Line 54: | Line 56: | ||
>/dev/pty/2 </dev/pty/2 | >/dev/pty/2 </dev/pty/2 | ||
− | If you want to use the terminal to send input to your | + | If you want to use the terminal to send input to your application, then you may need to stop the shell in it from reacting to the input (unless you started a terminal without a shell). |
Run something like | Run something like | ||
<syntaxhighlight lang="bash"> | <syntaxhighlight lang="bash"> | ||
Line 63: | Line 65: | ||
==== Debugger startup options ==== | ==== Debugger startup options ==== | ||
− | In the global options dialog, on the debugger page, you can specify | + | In the global options dialog, on the debugger page, you can specify parameters given to gdb (do '''not''' use the in/output redirect ">" / "<" here, use something like --args). |
It may be possible to specify the pty here, but there is currently no further info. | It may be possible to specify the pty here, but there is currently no further info. |
Revision as of 16:16, 10 July 2014
Introduction
This page contains information on how to debug console applications in Lazarus. That is where to find the output (writeln) of your app, and where to type the input (readln).
This page was written for Lazarus 0.9.30 and above.
Windows
On Windows, the application will open its own console window, just as it would outside the debugger. There is no need to do anything special.
Linux
Lazarus 0.9.30 / 0.9.30.2
Please see the notes in the#Mac section.
Lazarus 0.9.31 / 1.0 and higher
You can open a console window from the menu: "View" => "Debug Windows" => "Terminal Output"
It shows the raw output of your application. Note it has no support for any escape sequences, as some terminals may have.
Anything you type into this window will be sent to your application.
Mac
Unfortunately there is currently no built-in support for debugging console applications.
Console applications do not have their own terminal, but use the terminal they were started from (the terminal of the shell they were started from). When started from within Lazarus, there is no such terminal. You can specify a "starter application" (like xterm) under menu "Run" => "Run parameters". however this only works if you start your application without a debugger. This does not work for debugging.
There are a couple of workarounds.
Redirect output to file
In menu "Run" => "Run parameters": specify in "command line parameters":
>/somedir/somefile
Then outside Lazarus open a shell and run
tail -f /somedir/somefile
Redirect input and output to a pty (terminal)
Open a terminal outside of Lazarus and run
pty
It should return something like
/dev/pty/2
The exact value depends on the OS and the number of terminals already open.
- Note
- The returned value is only valid as long as the terminal stays open, so if you open a new terminal next time you debug in Lazarus, you need to adapt all settings to the new value.
In menu "Run" => "Run parameters": specify in "command line parameters":
>/dev/pty/2 </dev/pty/2
If you want to use the terminal to send input to your application, then you may need to stop the shell in it from reacting to the input (unless you started a terminal without a shell). Run something like
tail -f /some/empty/file/that/does/not/change
Debugger startup options
In the global options dialog, on the debugger page, you can specify parameters given to gdb (do not use the in/output redirect ">" / "<" here, use something like --args).
It may be possible to specify the pty here, but there is currently no further info.
Lazarus 0.9.31
In the global options dialog, on the debugger page is an entry "ConsoleTty". You can enter the result of "pty" here. Then you do not need to specify any "<" / ">" redirects.