Re: mod_perl debugging application debugging in shared environments

Still would be useful to get something more solid going - but I agree, 
for the time being, I'll might just as well go with what your suggesting.

I also looked at edebug, looks pretty cool and might be something I can 
use to setup a viable debugging environment for my situation - even 
better it seems to support remote debugging out of the box (more or 
less), and adding support to IDEs doesn't seem that difficult. Will 
definitely spend some time looking at it.

Thanks for your help,
Dmitriy.

On 11/18/2011 4:36 PM, Perrin Harkins wrote:
> On Fri, Nov 18, 2011 at 3:58 PM, Dmitriy Ryajov<[email protected]>  wrote:
>> The reasons are mostly legal, the client simply won't allow me to set it up
>> outside the dedicated server. There are also technical reasons, the system
>> is massive and too tight up to the rest of their internal infrastructure.
>> I'm working with an ssh session with the code pulled to my home and mapped
>> to a virtual host in apache 2.2, the rest of the devs are working in the
>> same manner under that same Apache server.
> Ok, what I would do in this situation is run my own apache on a high
> port on that same server.  I'd copy the conf file, change the port,
> and run httpd with my custom conf.  It's still on the same server,
> still has access to everything, but can be run under the debugger.
>
>> To repeat my question, are there any specific reasons, besides output
>> redirection that prevent the debugger running in a
>> multiprocess/multi-threaded host?
> None that I know of, but this is outside of my expertise.  I remember
> seeing some stuff about debugging forked processes on PerlMonks,org.
> You might want to have a look there.
>
> - Perrin