Normaly, ctrl +c works for a simple modperl program, I am trying to debug a more complex modperl program.
I'd like to provide all info you need, maybe I need some guide on what's needed. What I want to do is stepping into the modperl2 WebGUI program(https://svn.webgui.org/svnroot/WebGUI/ and fix some bugs. When I request the home page, I get the prompt of the debugger, then I input command 'r' to let debugger return from the contentHandler(), and input many other 'r' to return too, I just want to see if I can see the home page under debugging mode, but I can't, only lots of IO::Handle::DESTROY, and finally, hang there, I can't input any more debugger command, kill the apache2 process is the only thing left could be done. And on the browser side, I see from the status bar it is still waiting to dowload the .gif images, however, if trun the debugging mode off, home page can be displayed smoothly. In my httpd.conf, I enabled Apache2::Reload and Apache2::Status. Anything I missed or anything you want to know, please let me know. On 2/13/06, Perrin Harkins <[EMAIL PROTECTED]> wrote: > Ken Perl wrote: > > I tried to stop apache by issuing apache2ctl -k stop in another > > terminal, the command exit without any output, but the debugger is > > still hung there. I have to send signal KILL to the process. > > That will work, but the usual way to stop is to hit Ctrl-C in the > debugger terminal. The apache2ctl script probably fails because you are > running with a single process so the PID file isn't there or isn't accurate. > > I haven't seen your IO::Handle issue before, but I suspect the debugger > is just informing you about some code that ran after your return. The > real issue is why your home page doesn't display as you expect. To help > you with that, you need to give us more details about what happens and > what was supposed to happen. > > - Perrin > -- perl -e 'print unpack(u,"62V5N\"FME;G\!E<FQ`9VUA:6PN8V]M\"[EMAIL PROTECTED] ")'