|
Size: 385
Comment:
|
Size: 2179
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Pasquale is my name and I feel comfortable when people use the full name. One of my favorite hobbies is to do cryptography and I'll be starting something else along with it. Interviewing is what I do for a living. Kentucky is our birth place but my wife wants us to move. My wife and I maintain a website. You might want to check it out here: http://www.msfera.pl/ekshibicjonizm.html | Mercurial has a bunch of features for debugging problems that are useful for developers to know about. See also: DebuggingTests |||||| '''Global Options''' || || {{{-v, --verbose}}} || show more verbose output || || {{{--debug}}} || show extended debugging output || || {{{--traceback}}} || show Python tracebacks that are otherwise hidden || || {{{--profile}}} || generate performance profiling information || || {{{--debugger}}} || drop into the built-in source-level debugger (more below) || . |||||| '''Debug Commands''' || || {{{ debugcheckstate }}} || validate the correctness of the current dirstate || || {{{ debugconfig }}} || show combined config settings from all hgrc files || || {{{ debugdata }}} || dump the contents of an data file revision || || {{{ debugindex }}} || dump the contents of an index file || || {{{ debugindexdot }}} || dump an index DAG as a .dot file || || {{{ debugrename }}} || dump rename information || || {{{ debugstate }}} || show the contents of the current dirstate || || {{{ debugwalk }}} || show how files match on given patterns || To get a complete up-to-date list of all available debug commands use {{{hg debugcomplete debug}}}: {{{ > hg debugcomplete debug debugancestor debugcheckstate debugcomplete debugconfig debugdata debugdate debugfsinfo debugindex debugindexdot debuginstall debugrawcommit debugrebuildstate debugrename debugsetparents debugstate debugwalk }}} Documentation for some debug commands is available through {{{hg help}}}: {{{ > hg help debugstate hg debugstate show the contents of the current dirstate use "hg -v help debugstate" to show global options }}} === using the debugger === {{{hg --debugger <command>}}} will drop you at the debug prompt shortly before command execution. This will allow you to set breakpoints, singlestep code, inspect data structures, and run arbitrary bits of Python code. Help is available with '?'. If you let Mercurial run (with 'cont'), the debugger will be reinvoked if an exception occurs. This is useful for diagnosing tracebacks in situ. ---- CategoryInternals |
Mercurial has a bunch of features for debugging problems that are useful for developers to know about.
See also: DebuggingTests
Global Options |
||
-v, --verbose |
show more verbose output |
|
--debug |
show extended debugging output |
|
--traceback |
show Python tracebacks that are otherwise hidden |
|
--profile |
generate performance profiling information |
|
--debugger |
drop into the built-in source-level debugger (more below) |
|
Debug Commands |
||
debugcheckstate |
validate the correctness of the current dirstate |
|
debugconfig |
show combined config settings from all hgrc files |
|
debugdata |
dump the contents of an data file revision |
|
debugindex |
dump the contents of an index file |
|
debugindexdot |
dump an index DAG as a .dot file |
|
debugrename |
dump rename information |
|
debugstate |
show the contents of the current dirstate |
|
debugwalk |
show how files match on given patterns |
|
To get a complete up-to-date list of all available debug commands use hg debugcomplete debug:
> hg debugcomplete debug debugancestor debugcheckstate debugcomplete debugconfig debugdata debugdate debugfsinfo debugindex debugindexdot debuginstall debugrawcommit debugrebuildstate debugrename debugsetparents debugstate debugwalk
Documentation for some debug commands is available through hg help:
> hg help debugstate hg debugstate show the contents of the current dirstate use "hg -v help debugstate" to show global options
using the debugger
hg --debugger <command> will drop you at the debug prompt shortly before command execution. This will allow you to set breakpoints, singlestep code, inspect data structures, and run arbitrary bits of Python code. Help is available with '?'.
If you let Mercurial run (with 'cont'), the debugger will be reinvoked if an exception occurs. This is useful for diagnosing tracebacks in situ.