That's odd. Were you, by chance, using the "stop" option to get a reading without actually running the application? Because one limitation it does have is that modules loaded dynamically at run-time don't show up during the initial compile phase. If you ran the application from start to end, I would think it would catch these extras.

(The same thing would happen with plain-old DBI and any associated drivers.)

Nope - I got the output of the script, followed by the module use information. I used the first example in the Synopsis section. It was just the one-liner. I'd cut-n-paste the results but I don't have access to the server I was using it on right now.

Huh. Well, if you (or anyone else reading) can come up with a fairly small failure-case, I'll be happy to pick it apart and try to find the bug.

--rjray