I can't expect that you'll still remember this thread. However, I think I may have stumbled on to the solution. To recap, whenever I'd try Embperl 2.x I would be able to segfault httpd threads. If I ran 'httpd -X' I could crash the web server with just a few refreshes of an epl page. However, if I ran Embperl 1.x I was able to run it fine. My experimentation with 2.x vs 1.x was holding up my project so I had to just leave it at 1.x so I could get some work done. That's why I'm replying to an email over a month old.

Well, I stumbled on to this page recently while looking into setting up my new Powerbook G4 for Embperl development.
http://www.ecos.de/~mailarc/embperl/2002-08/msg00124.html


The important part is where you say... "Don't use ClearModuleList in your httpd.conf (this currently applies to all systems, with Apache 1.x and Embperl 2)". I'd never read that elsewhere and considering I'm using Apache 1.x I was eager to give it a try. Lo and behold, it seems to have resolved the issue. I've just done a couple of informal tests but I'm hopeful.

I just wanted to follow up with you so you could confirm or deny the question of Embperl 2.x, Apache 1.x and "ClearModuleList" in httpd.conf. I'll cc the list in case this information is helpful to others. Thanks.

Saadiq

On Friday, January 31, 2003, at 12:00 AM, Gerald Richter wrote:


Sadly, the only thing it changes is that with "Embperl_Debug 1" added, apache won't start. Configtest says ok but it won't start.


Any errors in the error log? or does it segfault?


Gerald



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to