← Back to branch summary

~bzr-pqm/bzr/bzr.dev

« back to all changes in this revision

Viewing changes to doc/en/developer-guide/HACKING.txt

  • Committer: John Arbash Meinel
  • Date: 2009-07-31 14:52:10 UTC
  • mto: This revision was merged to the branch mainline in revision 4580.
  • Revision ID: john@arbash-meinel.com-20090731145210-mdb6gt75s1dqddx9
NEWS and HACKING entries.

Show diffs side-by-side

added added

removed removed

Lines of Context:
doc/en/developer-guide/HACKING.txt
1167
1167
then bzr will go into pdb post-mortem mode when an unhandled exception
1168
1168
occurs.
1169
1169
 
1170
 
If you send a SIGQUIT signal to bzr, which can be done by pressing
1171
 
Ctrl-\\ on Unix, bzr will go into the debugger immediately.  You can
1172
 
continue execution by typing ``c``.  This can be disabled if necessary
1173
 
by setting the environment variable ``BZR_SIGQUIT_PDB=0``.
 
1170
If you send a SIGQUIT or SIGBREAK signal to bzr then it will drop into the
 
1171
debugger immediately. SIGQUIT can be generated by pressing Ctrl-\\ on
 
1172
Unix.  SIGBREAK is generated with Ctrl-Pause on Windows (some laptops have
 
1173
this as Fn-Pause).  You can continue execution by typing ``c``.  This can
 
1174
be disabled if necessary by setting the environment variable
 
1175
``BZR_SIGQUIT_PDB=0``.
1174
1176
 
1175
1177
 
1176
1178
Debug Flags