-----Original Message----- >From: Nathan Waddell [mailto:[EMAIL PROTECTED] >Sent: 18 January 2008 15:29 >To: The elegant MVC web framework >Subject: Re: [Catalyst] Debugging Catalyst with Eclipse > >Wow, thanks for all the responses. > >Troy, I'll subscribe to the EPIC list and see if I can get a >conversation started on their end. > >Matt, I guess you're a member of the EPIC list? > >Dmitriy, how did you set up Eclipse+EPIC to debug Catalyst apps? > >Peter, the Devel::ebug as remote debugger sounds promising. However, >I'm brand new to Catalyst, so I'll have to dig into the docs on that >and see if I can figure it out. Thanks for the suggestion!
Hi Nathan. Hooking Eclipse + EPIC to Devel::ebug is a separate issue from using Catalyst. I'd suggest aiming first to be able to remotely debug a "hello world!" program. Catalyst has a lot of debugging stuff built in, script/myapp_test.pl front end, Test::WWW::Mechanize wrapper, mock objects, fake requests and so on, which is where Matt's offer to help might come in handy if you want to add some Catalyst-specific goodies to the Eclipse front end that make use of its internals. Finally, to debug mod_perl problems (the few that you can't fix with log4perl prints, Mech tests and so on), it would be handy to have a front end option to invoke a debug Apache. You can do this with something like "httpd -f myhttpdebug.conf -X -DPERLDB" and use Apache::DB ins the .conf file. More pointers here http://www.perl.com/pub/a/2006/02/09/debug_mod_perl.html?page=2 Regards, Peter http://perl.dragonstaff.co.uk _______________________________________________ List: [email protected] Listinfo: http://lists.scsys.co.uk/cgi-bin/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
