kdb_cmds: new (returning) user questions
randy.dunlap at verizon.net
Tue May 15 16:42:45 PDT 2007
I have a few basic questions.
1. Is there a way to "import" custom kdb commands other than
putting them into kdb_cmds and rebuilding the kernel?
2. I'd like to be able to "bc all" (or "bca"). or I can put
that into a custom defcmd... Should I just do the latter?
3. I often need to use what some debuggers call "step over",
i.e., execute a call instruction and break after it returns,
immediately after the call instruction. Does kdb already have
this command and I just don't see it? Currently I just use:
defcmd soc "" "step over call"
bp %rip+5 # CPU-specific
but that leaves me with (should be temporary) breakpoints that
should be deleted ASAP. Can I determine what bpnum was used and
then clear it later? (although I don't know when I would clear it)
4. Is there a way to print (decode) the CPU flags register so that
I can see which bits (conditions) are set/clear?
*** Remember to use Documentation/SubmitChecklist when testing your code ***
Use http://oss.sgi.com/ecartis to modify your settings or to unsubscribe.
More information about the kdb