Hans-Ruodi Burch (EA/EAS) wrote:
Yes, right, but I run the make test at the 25th and the core file was
from

the 23rd. That's why I wrote, there is no core file. But to be sure I just tried it again:

23rd and 25th are dates? What's the output of your t/logs/error_log? Does
it say anything about segfaults (most likely). Perhaps it doesn't have
the right to dump the file? what happens if you run the test as non-root?




The core file from the 23rd is from the standard mod_perl 1.99_09 make test without any changes. Philippe ask me to modify the software and to re-run the make test, this was done at the 25th without any core dump.

So Philippe's patch fixes the segfault problem.


I did the same again last week, still with the modification from Philippe.
Please find the error_log attached (is it ok to send small attachments?).

Sure, attachments are fine, but better inlined so one doesn't have to save the file away just to view it. However this particular attachment has no added value, since it just says segfault about 150 times.


I don't think it is an authority problem, because I got a core file at the
23rd. However I run the make test with my userid with the following result:

of course, you must fix the permissions of the filesystem first, so that the non-root user can write there. let's say that your username and groupname is hans, then you need to do:


su
chown -R hans.hans
make test

run tests .(13)Permission denied: httpd: could not open error log file
/usr/local/source/perl-5.8.0-modules/mod_perl-1.99_09/t/logs/error_log. Unable to open logs


__________________________________________________________________
Stas Bekman            JAm_pH ------> Just Another mod_perl Hacker
http://stason.org/     mod_perl Guide ---> http://perl.apache.org
mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com
http://modperlbook.org http://apache.org   http://ticketmaster.com


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



Reply via email to