Re: add a very useful command to ddb

Given a function(such as amap_alloc), can you quickly find out how it works? In the most common way, you must use info function command in gdb to see which source file contains this function, and then open it, check the subroutines it calls, and use info function command again to see where those subroutines reside, in order to find recursively all subroutines directly or indirectly called, what a boring work, and you have to select(maybe guess) some subroutines you think important, set breakpoints on them one by one, then you can use bt, up, down command to get the information, and you still may be puzzled with the runtime execution flow, for example, it is a difficult way to know how a loop is performed, what runtime parameters a subroutine in this loop is called with, it may take you up to a whole day when explore a complicated function in kernel(because you may reboot several times to reproduct the condition you need to debug).but with the single command yzw, you can get all of them.

• Original Message ----- From: "Teh Kok How" <khteh@willowglen.com.my> To: "ÑîÖÂΰ" <yangzw@cn.is-one.net> Sent: Tuesday, July 01, 2003 8:49 AM Subject: Re: add a very useful command to ddb

> Hi;
> This functionality can be achieved with 'backtrace', 'bt', 'up' and 'down'
> which are already in the gdb. How different is yours from the standard
one?
>
> Teh
>
> On Tuesday 20 May 2003 11:48, ÑîÖÂΰ wrote:
> > unlike n/p, yzw command use another way to print more readable
infomation
> > of function's calling tree, and their arguments.
it,
> > with just one command, we can monitor all the arguments we passed in.
version
> > of OpenBSD.
knowledge
> > about other archs
Received on Mon Jun 30 23:33:55 2003