Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
1.1.0 | 2019-11-04 | ||
1.0.0 | 2019-11-02 | ||
0.07 | 2018-06-21 | ||
0.06 | 2011-05-19 | ||
0.05 | 2011-03-15 | ||
0.04 | 2009-10-27 | ||
0.03 | 2009-07-04 | ||
0.02 | 2009-06-13 | ||
0.01 | 2008-11-17 | ||
README | 2011-05-20 | 1.7 kB | |
Totals: 10 Items | 1.7 kB | 0 |
0. INTRODUCTION This is a port and cleanup of my bash debugger bashdb (http://bashdb.sf.net). The command syntax generally follows that of the GNU debugger gdb. However this debugger depends on a number bug fixes and of debugging support features that are neither part of the POSIX 1003.1 standard and only in ksh93t+ releases. In particular, there are fixes to a number of the .sh variables like .sh.level and .sh.file. 1. SETUP See https://github.com/rocky/kshdb/wiki/How-to-install for how to install this code. 2. WHAT'S HERE, WHAT'S NOT and WHY NOT What's missing falls into a two categories: * Stuff that can be ported in a straightforward way from bashdb * Stuff that needs additional ksh support Of the things which can be ported in a straight-forward way, however some of them I want to revise and simplify. In some cases, the fact that ksh has associative arrays simplifies code. On other cases, the code I wrote needs refactoring and better modularization. Writing documentation is important, but an extensive guide will have to wait. For now one can consult the reference guide that comes with bashdb: http://bashdb.sf.net/bashdb.html There is some minimal help to get a list of commands and some help for each. 3. WHAT'S NOT HERE YET IN DETAIL This can done with or without support from ksh, albeit faster with help from ksh. 3.a) Setting $0 3.b) lots of other stuff including... display expressions, signal handling, debugger commands: debug file handle history signal tty watch None of this is rocket science. Should be pretty straight-forward to add. 4. WHAT MAY NEED MORE WORK AND SUPPORT FROM KSH 4.a) stopping points that can be used for breakpoint