Re: Remote debugging problem

I have a couple of thoughts. The %INC hash contains all the packages (and required scripts) that are loaded and where they are loaded from. So you could dump %INC to find out where perldb5.pl is getting perl5db

PERLDB_OPTS="NonStop=1" perl -de "while(my(\$key, \$value) = each(%INC
+)){print qq{\$key ==> \$value\n};}"
perl5db.pl ==> /usr/lib/perl5/5.8.0/perl5db.pl
[download]

Also, rather than using an environment variable to tell perl where to look for the package, you could use the -I option:

(foo-lnx:Mon Jan 10 14:53:14):~/tmp
$cp /usr/lib/perl5/5.8.0/perl5db.pl .
 
(foo-lnx:Mon Jan 10 14:53:31):~/tmp
$PERLDB_OPTS="NonStop=1" perl -I. -de "while(my(\$key, \$value) = each
+(%INC)){print qq{\$key ==> \$value\n};}"
perl5db.pl ==> perl5db.pl
[download]

Hope that helps!

Sorry, can't help with the RemotePort portion as I don't use Active State.

"Look, Shiny Things!" is not a better business strategy than compatibility and reuse.

Comment on Re: Remote debugging problem Select or Download Code

Replies are listed 'Best First'.
Re^2: Remote debugging problem by robhuffstedtler (Initiate) on Jan 11, 2005 at 16:00 UTC
Thanks. I don't know why it didn't occur to me that perl5db.pl would be listed in %INC. I was, in fact, still including the wrong one, apparently because of the quotes aroung the path in the value for PERL5LIB. I fixed that, and it is now including the right one, but it's still griping about not recognizing the option. I guess it's time to dig into the source for ActiveState's version of the debugger and see if anything leaps out at me.	[reply]
Re^3: Remote debugging problem by osunderdog (Deacon) on Jan 11, 2005 at 16:13 UTC
Not to Troll too much, but if it was open source I could probably help figure out why it isn't working. (Because I would be using the heck out of it.) *"Look, Shiny Things!"* is not a better business strategy than compatibility and reuse.	[reply]
Re^4: Remote debugging problem by robhuffstedtler (Initiate) on Jan 11, 2005 at 16:42 UTC
Ah ha! Exact same problem. I should have read the documents more carefully. Apparently you only need the quotes around the value for the environment variables on unix/linux. I still don't have it working, but at least I've moved on to another problem :)	[reply]
Re^5: Remote debugging problem by osunderdog (Deacon) on Jan 11, 2005 at 16:47 UTC