commit | 04c5d2ee7236d37c7c9cf322f1d2ecccfc1966c5 | [log] [tgz] |
---|---|---|
author | Nick M. Mitchell <nickm@us.ibm.com> | Fri Sep 30 11:13:37 2016 -0400 |
committer | Nick M. Mitchell <nickm@us.ibm.com> | Fri Sep 30 11:13:37 2016 -0400 |
tree | ea6a91cea7b02080edb11e46922c6d154437a5d9 | |
parent | a6421d43db4ede03ac18cbce40eed7b8e78586e3 [diff] |
update to the new home of the public owdbg package
This project currently supports debugging NodeJS actions on your laptop.
Start the debug client:
% (cd client; ./wskdb) Welcome to the OpenWhisk Debugger ? (wskdb)
You will now be in a REPL. Issue help
to see the list of available commands.
The syntax here is almost identical to that of the wsk
CLI.
? (wskdb) invoke actionName -p param1 value1 -p param2 value2
If you haven‘t yet attached to the action you are invoking, the invocation will proceed as if you weren’t in the debugger, and had issued a blocking invocation from the CLI.
Say for example you wish to attach to an action foo
, and this action occurs in a sequence seq
.
? (wskdb) attach foo Attaching to foo Creating action trampoline Creating sequence splice seq