3761bead4a
Before executing a command in a ddb script ddb prints an information line of the form: db:1:my-script> command where 1 is the script's depth level, "my-script" is the scipt's name, and "command" is the current command in the script. db_script_exec() uses its 'scriptname' parameter to produce that string. In the case when db_script_exec() is called from db_run_cmd() the argument points to db_tok_string that is a global variable used for command parsing. So, its value changes with every command executed. This commit changes the code to use the script's name stored in ds_scriptname to print the line. MFC after: 2 weeks |
||
---|---|---|
.. | ||
db_access.c | ||
db_access.h | ||
db_break.c | ||
db_break.h | ||
db_capture.c | ||
db_command.c | ||
db_command.h | ||
db_examine.c | ||
db_expr.c | ||
db_input.c | ||
db_lex.c | ||
db_lex.h | ||
db_main.c | ||
db_output.c | ||
db_output.h | ||
db_print.c | ||
db_ps.c | ||
db_run.c | ||
db_script.c | ||
db_sym.c | ||
db_sym.h | ||
db_textdump.c | ||
db_thread.c | ||
db_variables.c | ||
db_variables.h | ||
db_watch.c | ||
db_watch.h | ||
db_write_cmd.c | ||
ddb.h |