Browse Source

helper: add stacktrace command that returns error stacktrace

Ability to access the stacktrace from a script is quite
handy.

Signed-off-by: Øyvind Harboe <oyvind.harboe@zylin.com>
tags/v0.5.0-rc1
Øyvind Harboe 13 years ago
parent
commit
8afd2309a4
1 changed files with 31 additions and 0 deletions
  1. +31
    -0
      src/openocd.c

+ 31
- 0
src/openocd.c View File

@@ -185,6 +185,29 @@ COMMAND_HANDLER(handle_add_script_search_dir_command)
return ERROR_OK;
}


static int jim_stacktrace_command(Jim_Interp *interp, int argc,
Jim_Obj * const *argv)
{
if (argc != 1)
{
return JIM_ERR;
}
Jim_Obj * stacktrace = Jim_DuplicateObj(interp, interp->stackTrace);
/* insert actual error site at beginning of list*/
Jim_Obj *procname = Jim_NewStringObj(interp, "", -1); /* Uhhh... don't know this one. */
Jim_ListInsertElements(interp, stacktrace, 0, 1, &procname);
Jim_Obj *filename = Jim_NewStringObj(interp, interp->errorFileName, -1);
Jim_ListInsertElements(interp, stacktrace, 1, 1, &filename);
Jim_Obj *line = Jim_NewIntObj(interp, interp->errorLine);
Jim_ListInsertElements(interp, stacktrace, 2, 1, &line);

Jim_SetResult(interp, stacktrace);

return JIM_OK;
}

static const struct command_registration openocd_command_handlers[] = {
{
.name = "version",
@@ -215,6 +238,14 @@ static const struct command_registration openocd_command_handlers[] = {
.help = "dir to search for config files and scripts",

},
{
.name = "stacktrace",
.jim_handler = jim_stacktrace_command,
.mode = COMMAND_ANY,
.help = "returns the stacktrace as a list of triples: proc, file, line."
"The stack trace is reset when a new stack trace is being built after "
"a new failure has occurred.",
},
COMMAND_REGISTRATION_DONE
};



Loading…
Cancel
Save