default remote connection usage

[jamie]

I'm trying to get the hang of using winpdb and the packaged version of
rpdb2 for remote debugging.

As far as I can tell, rpdb2 -r <scriptname> generates a random
password, doesn't disclose it, writes it to a file, attaches to the
script, and then kills the file. Since the password file gets deleted
way too fast to reference, from a practical standpoint, what is the
general approach for remote attaching via winpdb?

I can add code manually to prevent the password file from being
deleted, and that works, but I think I have to be missing something as
if I really have to add in additional code, then what's the point of
the -r flag?

Since I'm running on linux, the --pwd option is disallowed, so my
basic question is : if I can't specify the password, and the
autogenerated password vanishes in the blink of an eye, what should I
be doing?

[Nir Aides]

Try the -d flag
Alternatively try the password console command.

--
You received this message because you are subscribed to the Google Groups "Winpdb" group.
To post to this group, send email to win...@googlegroups.com.
To unsubscribe from this group, send email to winpdb+un...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/winpdb?hl=en.