[Dev] Debugging Chandler threads with WingIDE?

[Heikki Toivonen]

Andi Vajda wrote:
> On Mon, 13 Feb 2006, Heikki Toivonen wrote:
>> It's not about command line vs GUI.
> 
> Then what is it about ?
> If it is changing the code to set a breakpoint that bothers you then you
> can use the more common - but slower - way which is to start the process
> in pdb and set a breakpoint using the 'break' command as you'd do in gdb
> before running the program.

Does pdb let me set breakpoint in a file that has not yet been imported?
(This is more like a usability point, not actually my main concern.)

Suppose I have set two breakpoints: one on a line that gets run by the
main thread and one on a line that only gets executed in a background
thread. Will pdb break for both?

> Normally, when you debug a C program you don't go around adding signal
> calls to enter the debugger because recompiling and rebuilding takes a
> while.
> This being python, it's not an issue, changing code to set a breakpoint
> is as fast, if not faster, than the 'break' command way.

Well, it is still an issue, because whenever you edit the code to add
some stuff you only use for debugging you also have to remember to undo
that before checking in. I'd like to avoid this.

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/dev/attachments/20060213/12596137/signature.pgp