Hi Paul, Thanks a lot for your reply!
After I turned off warning in all my product scripts and test scripts which I was running Devel::Cover on, 90% warning messages related B::Deparse deep recursion have gone, and only a few were left in logs. So, from your email, seems like, in order to completely remove those B::Deparse deep recursion warnings from my test log, I should also add "no warnings" in Devel::Cover code to customize this model and disable warning in it, please advice if my understanding and approach is right or not. Thanks, Scott --- Paul Johnson <[EMAIL PROTECTED]> wrote: > On Sat, Jun 03, 2006 at 08:29:09PM -0700, Scott Wang > wrote: > > > Thanks!...Scott > > Does this mean everything is working OK for you? > > "Deep recursion on subroutine" is just a warning, > though Devel::Cover > seems to tickle it through B::Deparse fairly > regularly. I'll try to do > something about that one way or another. > > B::Deparse is used to display the code used in > branches and conditions, > and also as a handy tool for walking through a > complete optree doing > stuff at each op. > > With respect to "cover" using a lot of memory, yes, > I'm afraid that > could happen with large databases. The reason is > that the database is > read into a perl data structure. (The "database" is > really little more > than a Storable dump of a Devel::Cover::DB object.) > I'm afraid that the > pragmatic approach its probably to throw RAM at the > hardware. > > -- > Paul Johnson - [EMAIL PROTECTED] > http://www.pjcj.net > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com