Hi, While testing the (almost finished) Debian package of padre 0.59, this is what happened:
I ran padre from my home directory, loaded a file, moved the cursor to the end, over an exit() call and pressed F2. A new window appeared, saying 'Reading items. Please wait.'. Then my disk started seeking and padre appeared to be stuck. Poking with lsof showed that padre walks over my home directory contents. I have a huge home directory (a Svn checkout of all the perl module packages handled by the Debian Perl Group -- over 1600), so I interrupted it. Further investigation shows that padre tries to find all available Perl modules via the _find_installed_modules routine in Padre::Document::Perl::Help. This involves recursively scanning all directories foind in @INC. For some reason, perl's @INC on Debian includes the '.' directory, and since I started padre from my home directory, I got a nice DoS. My proposal is to skip searching the '.' directory in _find_installed_modules. An IRC query suggested that I mail before committing, so here we go :) Are there objections against skipping '.' when finding installed modules?
signature.asc
Description: Digital signature
_______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev
