Re: Prb: Apache::DB plus Perl 5.6 doesn't break

2000-05-19 Thread Doug MacEachern

i hadn't tried Apache::DB with newer Perl since 5.005_6x-ish, there was a
fix that went into version 0.06 for that, are you using 0.06?

i am able to set breakpoints no problem with 5.6.0 (perl-current,
actually).  i would suggest stripping back your Perl config to something
simple (i tested with b Apache::Status::handler) and make sure
require Apache::DB/Apache::DB-init is the first piece of Perl code to
run.




Re: Prb: Apache::DB plus Perl 5.6 doesn't break

2000-05-19 Thread Jeremy Howard

 i am able to set breakpoints no problem with 5.6.0 (perl-current,
 actually).  i would suggest stripping back your Perl config to something
 simple (i tested with b Apache::Status::handler) and make sure
 require Apache::DB/Apache::DB-init is the first piece of Perl code to
 run.
 
Thanks heaps, Doug--moving require Apache::DB/Apache::DB-init to the top fixed it!

Previously I had 'use Apache' 1st, which worked fine under the "old" version... It's 
funny the things that change between versions, isn't it? In fact, Apache::DB is now 
working better than before--I used to have some subs outside of modules that wouldn't 
break properly... now they work fine!

Is anyone aware of any specific reason not to switch to 5.6.0 with mod_perl for 
production machines (other than just 'in case')?

-- 
  Jeremy Howard
  [EMAIL PROTECTED]



Re: Prb: Apache::DB plus Perl 5.6 doesn't break

2000-05-19 Thread Doug MacEachern

On Fri, 19 May 2000, Jeremy Howard wrote:

 Thanks heaps, Doug--moving require Apache::DB/Apache::DB-init to the
 top fixed it! 

kool!

 Previously I had 'use Apache' 1st, which worked fine under the "old"
 version... It's funny the things that change between versions, isn't it?
 In fact, Apache::DB is now working better than before--I used to have
 some subs outside of modules that wouldn't break properly... now they
 work fine!   

right, because Perl decides at compile time if a subroutine call should be
dispatched to the debugger, which it won't do unless Apache::DB-init has
been called (similar to what -d switch does on the command line)
 
 Is anyone aware of any specific reason not to switch to 5.6.0 with
 mod_perl for production machines (other than just 'in case')? 

we've hit a few problems, but 1.24 should have them ironed out. can't
promise there won't be more though.




Prb: Apache::DB plus Perl 5.6 doesn't break

2000-05-18 Thread Jeremy Howard

Well, that subject line looks a bit odd, doesn't it? What I mean is that with Perl 
5.6.0, Apache::DB is broken, because it doesn't break... Er, that is, you can add 
breakpoints, but Apache::DB never actually breaks on them.

Is anyone else having this problem? Is there a new version in the works?

-- 
  Jeremy Howard
  [EMAIL PROTECTED]



Re: Prb: Apache::DB plus Perl 5.6 doesn't break

2000-05-18 Thread Jeremy Howard

 Well, that subject line looks a bit odd, doesn't it? What I mean is that
 with Perl 5.6.0, Apache::DB is broken, because it doesn't break... Er,
 that is, you can add breakpoints, but Apache::DB never actually breaks on
 them.
 
 Is anyone else having this problem? Is there a new version in the works?

I've got a bit more info on this now. Nothing has changed on my PC (Linux RH 6.2) 
since this morning, other than updating Perl from 5.005_03 to 5.6.0. Apache::DB _was_ 
working fine.

When I add a breakpoint, tab completion works fine to enter a sub name, and no errors 
are given by the debugger. However, doing an 'L' doesn't show any breakpoints, and no 
breaks occur.

I've tried replacing perl5db.pl in 5.6.0 with the version from 5.005_03, but the 
behaviour is the same.

Anyone else having this trouble? Anyone successfully used Apache::DB in 5.6.0?


-- 
  Jeremy Howard
  [EMAIL PROTECTED]