src/sys/ddb/db_command.c, branch release/6.3.0 FreeBSD source tree https://cgit-dev.freebsd.org/src/atom?h=release%2F6.3.0 2007-10-23T16:07:30Z MFC: rev. 1.61: remove the need to forward declare statics. 2007-10-23T16:07:30Z David E. O'Brien obrien@FreeBSD.org 2007-10-23T16:07:30Z urn:sha1:4106dcc8958d8fe88a4f801e3cbfaad61b8e5bfe MFC: Remove sparc64 & PowerPC MD 'reboot' and 'halt' commands and make them 2007-10-19T16:48:43Z David E. O'Brien obrien@FreeBSD.org 2007-10-19T16:48:43Z urn:sha1:9c9c02f297a9699f72c518aec81805ba3cf226d0 MI. 'reboot' is an alias for 'reset'. MFC: Rename 'traceall' to 'alltrace' and add a 'bt' alias for 'trace'. 2005-10-25T20:10:56Z John Baldwin jhb@FreeBSD.org 2005-10-25T20:10:56Z urn:sha1:9248bc1cbbb38974ed453b479cb28b761c7427bc Approved by: re (scottl) Merge db_command.c:1.62 from HEAD to RELENG_6: 2005-10-06T13:15:21Z Robert Watson rwatson@FreeBSD.org 2005-10-06T13:15:21Z urn:sha1:14d8fd6077a3f2d9731d615d06fdcab6576b6e86 Add a DDB "traceall" function, which stack traces all known process threads. This is quite useful if generating a debug log for post-mortem by another developer, in which case the person at the console may not know which threads are of interest. The output of this can be quite long. Discussed with: kris Approved by: re (scottl) Implement functions calls from within DDB on ia64. On ia64 a function 2005-07-02T23:52:37Z Marcel Moolenaar marcel@FreeBSD.org 2005-07-02T23:52:37Z urn:sha1:a2aeb24eff776bef1e9afa2b2aa108e9fc4a3556 pointer doesn't point to the first instruction of that function, but rather to a descriptor. The descriptor has the address of the first instruction, as well as the value of the global pointer. The symbol table doesn't know anything about descriptors, so if you lookup the name of a function you get the address of the first instruction. The cast from the address, which is the result of the symbol lookup, to a function pointer as is done in db_fncall is therefore invalid. Abstract this detail behind the DB_CALL macro. By default DB_CALL is defined as db_fncall_generic, which yields the old behaviour. On ia64 the macro is defined as db_fncall_ia64, in which a descriptor is constructed to yield a valid function pointer. While here, introduce DB_MAXARGS. DB_MAXARGS replaces the existing (local) MAXARGS. The DB_MAXARGS macro can be defined by platforms to create a convenient maximum. By default this will be the legacy 10. On ia64 we define this macro to be 8, for 8 is the maximum number of arguments that can be passed in registers. This avoids having to implement spilling of arguments on the memory stack. Approved by: re (dwhite) Start each of the license/copyright comments with /*- 2005-01-06T01:34:41Z Warner Losh imp@FreeBSD.org 2005-01-06T01:34:41Z urn:sha1:dd3cb56845afea8d0480ed47caf7e5e415ab19e6 When printing a stack trace for a thread, also print the pid and tid. 2004-11-23T23:11:47Z Robert Watson rwatson@FreeBSD.org 2004-11-23T23:11:47Z urn:sha1:a13aca1a8e76765af911beabbded4e84b6d5703e When a series of traces is included in a bug report, this will make it easier to tie the trace information back to ps or threads output, each of which will show the pid or the tid, but usually not both. Oops... Add the CS_OWN flag to the trace and where commands so that 2004-07-21T05:55:51Z Marcel Moolenaar marcel@FreeBSD.org 2004-07-21T05:55:51Z urn:sha1:026c3aaa6080436ab7b80012b95a4a0ebaa3e7e5 db_stack_trace() actually has a chance to parse its own arguments. Unify db_stack_trace_cmd(). All it did was look up the thread given 2004-07-21T05:07:09Z Marcel Moolenaar marcel@FreeBSD.org 2004-07-21T05:07:09Z urn:sha1:fd32d93b97086acaf80526bbb55f735b35d074fb the thread ID and call db_trace_thread(). Since arm has all the logic in db_stack_trace_cmd(), rename the new DB_COMMAND function to db_stack_trace to avoid conflicts on arm. While here, have db_stack_trace parse its own arguments so that we can use a more natural radix for IDs. If the ID is not a thread ID, or more precisely when no thread exists with the ID, try if there's a process with that ID and return the first thread in it. This makes it easier to print stack traces from the ps output. requested by: rwatson@ tested on: amd64, i386, ia64 Re-add the gdb command. It was removed to be replaced by something 2004-07-12T01:38:07Z Marcel Moolenaar marcel@FreeBSD.org 2004-07-12T01:38:07Z urn:sha1:f3be7cb3e9c0d3621cd6b2e775aa1cbf77ec5eb6 more generic, but that didn't actually happen. Since the feature to switch backends (and historically this means from DDB to GDB) is important, make sure people can do just that until such the generic mechanism actually sees the light of day. Suggested by: rwatson@