[Catalyst] Debugging Catalyst with Komodo
Dami Laurent (PJ)
laurent.dami at justice.ge.ch
Fri Feb 2 07:15:57 GMT 2007
> -----Message d'origine-----
> De : Dan Dascalescu [mailto:ddascalescu+catalyst at gmail.com]
> Envoyé : vendredi, 2. février 2007 05:29
> À : The elegant MVC web framework; Development of the elegant
> MVC web framework
> Objet : [Catalyst] Debugging Catalyst with Komodo
>
> I'm running Catalyst 5.7006 on RHEL AS 4 and want to debug
> remotely with Komodo 4.0.0-beta4 on a Windows box. The
> problem is Komodo can only step through the initialization
> pars of the app, and execution never reaches breakpoints in
> controllers.
>
I think this is not due to Komodo, but to the fact that modules in a Catalyst app are loaded dynamically (after compile-time) by the Catalyst initialization code. So at the time you want to set your breakpoints, the modules are not loaded yet.
I don't know the proper solution to this, but I know a workaround : you can put the statement
$DB::single = 1;
somewhere in your code. This will force a breakpoint if running in -d mode (cf L<perldebug>). And then, since your modules are now loaded, you can add all your other breakpoints as usual.
Good luck, L. Dami
More information about the Catalyst
mailing list