Thanks! thats my favorite kind of discount ... free! I have used
debuggers before ie. gdb and ddd (which i think just runs gdb) but thats it.
-Justin
Leo Simons wrote:
Leo Simons wrote:
So, ehm, it is possible to run gump through pdb or another debugger
(like wing), but I've found none of those are really of sufficient
quality to be very productive. ye olde "print" statement works as well.
So, ehm, *cough*, I actually found myself explaining to adam the other
day how useful the Wing IDE debugger can be. I just committed some stuff
that hopefully makes it real easy to use either wing or PDB for
debugging. Let me know if it doesn't work.
Justin, you might want to try this out. You can get a free license to
Wing IDE for working on open source software (see
http://wingware.com/store/prices#discounts).
cheers,
Leo
Using a Real Debugger(tm) with Gump3
------------------------------------
Running `./gump help` shows two debug-related command line options:
debug -- run pygump in debug mode, attaching pdb
debug-with-wing -- run pygump in debug mode, attaching the Wing IDE
Which have docs:
[EMAIL PROTECTED] ./gump help debug
Run pygump in debug mode.
Usage:
./gump debug [gump.py-args ...]
This is not the same as executing the 'run' command with a '--debug'
parameter. Using this command will actually start the command line
debugger pdb to run gump in, whereas the '--debug' option customizes
the log verbosity gump will use.
This command otherwise accepts the same arguments as the 'run'
command.
[EMAIL PROTECTED] ./gump help debug-with-wing
Gump3
Run pygump in debug mode.
Usage:
./gump debug [gump.py-args ...]
This is not the same as executing the 'run' command with a '--debug'
parameter. Using this command will actually start the debug connector
for the Wing IDE and attach it to the gump process, whereas the
'--debug' option customizes the log verbosity gump will use.
This command otherwise accepts the same arguments as the 'run'
command.
Usage is something like this:
./gump debug -w \
/home/lsimons/svn/gump/branches/Gump3/fixture/metadata/workspace.xml
or for wing ide:
export WINGHOME=path/to/wing/2
./gump debug-with-wing -w \
/home/lsimons/svn/gump/branches/Gump3/fixture/metadata/workspace.xml
If you've not worked with debuggers before, you should probably take
some time to review the relevant documentation for your choice of
- PDB: http://www.ferg.org/papers/debugging_in_python.html
- Wing IDE: http://wingware.com/doc/debug/index
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
