| Title: | Digital Ladebug debugger |
| Moderator: | TLE::LUCIA |
| Created: | Fri Feb 28 1992 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 969 |
| Total number of notes: | 3959 |
Using ladebug 4.0-26:
Typing the "rerun" command behaves differently between the GUI and the CLI:
The CLI will keep all command-line arguments
The GUI will destroy all command-line arguments
The GUI should act like the CLI. Consider the online docuemntation ("help
rerun"):
"....as arguments. If the 'rerun' command is specified without
arguments, the arguments entered with the previous 'run'
command are used. If the last modification time and/or ....."
Example:
#include <stdio.h>
main(int argc, char** argv) { printf ("argv[1] = '%s'\n", argv[1]); }
ladebug:
(ladebug) run foo
argv[1] = 'foo'
Process has exited with status 0
(ladebug) rerun
argv[1] = 'foo'
Process has exited with status 0
dxladebug output:
argv[1] = 'foo'
argv[1] = '(null)'
- Matt
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 806.1 | ADA9X::BRETT | Wed Feb 05 1997 14:17 | 6 | ||
This is a REAL pain. Especially since it usually hangs dxladebug so badly that you have to blow it away. /Bevin | |||||
| 806.2 | TLE::MURRAY | Wanfang Murray | Mon Feb 24 1997 07:39 | 18 | |
There are at least three problems when issuing rerun from the gui.
They are:
a. argument text field are cleared whenever "run the same
program" menu is selected
b. run arguments are not saved when the rerun command is
issued from the command/message view
c. "run the same program" doesn't refresh the source display
if the binary has changed.
We are working on these problems right now, and hope to include
in the next couple base level kits.
Wanfang
| |||||
| 806.3 | fixed in 4.0-33 | PACKED::ALLEN | Christopher Allen, Ladebug, dtn 381-0864 | Mon Mar 17 1997 10:26 | 0 |
| 806.4 | Thanks & a suggestion | CXXC::MJHANS | Matthew Hanselman, DEC C/C++ | Fri Apr 11 1997 16:57 | 16 |
This is fixed. It's very nice to now have a "rerun" button that reruns
everything & saves everything.
However, a quick suggestion to improve usability:
Is there any way for the GUI to query the engine for the current
arguments?
What I'm getting at: If I'm running the GUI, but run the program by
typing "run <arguments>" into the command-line portion, those arguments
will not show up if I choose "File->Rerun Same Program...". Yet if I
click "OK" on this dialog, it issues "rerun" to the engine, which uses
the arguments I had specified before. So this, to me, looks like I'm
running it the second time with no arguments, but I actually am.
- Matt
| |||||
| 806.5 | PACKED::ALLEN | Christopher Allen, Ladebug, dtn 381-0864 | Mon Apr 14 1997 12:25 | 3 | |
Thanks for this suggestion. It's on our list. -Chris | |||||