Re: Apache custom directives problem

2004-05-11 Thread Geoffrey Young
> { name => 'CASServerName', > errmsg => 'Name of the CAS server', > args_how => 'TAKE1', > req_override => 'OR_AUTHCFG', } > > quote > (gdb) bt > #0 0x0807d151 in perl_perl_create_cfg (sv=0x888fdcc, pclass=0x816fcc4, > parms=0xba10, type=0x80ed6c9 "SERVER_CREATE")

Re: Apache custom directives problem

2004-05-10 Thread Glenn
On Mon, May 10, 2004 at 02:55:34PM -0700, Stas Bekman wrote: > Anthony Hinsinger wrote: > >This is my xs file. it's 100% generated by Apache::Extutils. > > >static mod_perl_perl_dir_config *newPerlConfig(pool *p) > >{ > >mod_perl_perl_dir_config *cld = > >(mod_perl_perl_dir_config *) >

Re: Apache custom directives problem

2004-05-10 Thread Stas Bekman
Anthony Hinsinger wrote: This is my xs file. it's 100% generated by Apache::Extutils. static mod_perl_perl_dir_config *newPerlConfig(pool *p) { mod_perl_perl_dir_config *cld = (mod_perl_perl_dir_config *) palloc(p, sizeof (mod_perl_perl_dir_config)); cld->obj = Nullsv;

Re: Apache custom directives problem

2004-05-10 Thread Anthony Hinsinger
This is my xs file. it's 100% generated by Apache::Extutils. Anthony --- quote #include "modules/perl/mod_perl.h" static mod_perl_perl_dir_config *newPerlConfig(pool *p) { mod_perl_perl_dir_config *cld = (mod_perl_perl_dir_config *) palloc(p, sizeof (mod_perl_perl_d

Re: Apache custom directives problem

2004-05-10 Thread Stas Bekman
Anthony Hinsinger wrote: i restarted a gdb session so *sv has changed (backtrace is exactly the same as in previous post) That's normal. (gdb) p *sv $2 = (SV *) 0x2d656863 (gdb) p **sv Cannot access memory at address 0x2d656863 (gdb) So *sv is bogus. That means that data->obj is bogus in: #2 0

Re: Apache custom directives problem

2004-05-10 Thread Anthony Hinsinger
Stas Bekman wrote: Anthony Hinsinger wrote: Stas Bekman wrote: Anthony Hinsinger wrote: the missing lines : Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2752)] 0x0807d151 in perl_perl_create_cfg (sv=0x888fdcc, pclass=0x816fcc4, parms=0xba10, type

Re: Apache custom directives problem

2004-05-10 Thread Stas Bekman
Anthony Hinsinger wrote: Stas Bekman wrote: Anthony Hinsinger wrote: the missing lines : Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2752)] 0x0807d151 in perl_perl_create_cfg (sv=0x888fdcc, pclass=0x816fcc4, parms=0xba10, type=0x80ed6c9 "SERVER_CR

Re: Apache custom directives problem

2004-05-10 Thread Anthony Hinsinger
Stas Bekman wrote: Anthony Hinsinger wrote: the missing lines : Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2752)] 0x0807d151 in perl_perl_create_cfg (sv=0x888fdcc, pclass=0x816fcc4, parms=0xba10, type=0x80ed6c9 "SERVER_CREATE") at perl_config.c:

Re: Apache custom directives problem

2004-05-10 Thread Stas Bekman
Anthony Hinsinger wrote: the missing lines : Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2752)] 0x0807d151 in perl_perl_create_cfg (sv=0x888fdcc, pclass=0x816fcc4, parms=0xba10, type=0x80ed6c9 "SERVER_CREATE") at perl_config.c:898 898 if(*sv

Re: Apache custom directives problem

2004-05-10 Thread Anthony Hinsinger
the missing lines : Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2752)] 0x0807d151 in perl_perl_create_cfg (sv=0x888fdcc, pclass=0x816fcc4, parms=0xba10, type=0x80ed6c9 "SERVER_CREATE") at perl_config.c:898 898 if(*sv && SvTRUE(*sv) && SvROK(

Re: Apache custom directives problem

2004-05-10 Thread Stas Bekman
Anthony Hinsinger wrote: Hello, here is a better backtrace of my problem. the strange thing is it never crash at the first request after starting the process (from gdb) .. but at the second. for informations, CASServerName is define as : { name => 'CASServerName', errmsg => 'Name of the CAS

Re: Apache custom directives problem

2004-05-10 Thread Anthony Hinsinger
Hello, here is a better backtrace of my problem. the strange thing is it never crash at the first request after starting the process (from gdb) .. but at the second. for informations, CASServerName is define as : { name => 'CASServerName', errmsg => 'Name of the CAS server', args_how =>

Re: Apache custom directives problem

2004-05-10 Thread Stas Bekman
Anthony Hinsinger wrote: Thanks Stas, i use gdb to trace to problem, and i get this when requesting a location with a .htaccess contening my own directives (no problem if directives are in httpd.conf). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 28586)] 0x08

Re: Apache custom directives problem

2004-05-10 Thread Anthony Hinsinger
Thanks Stas, i use gdb to trace to problem, and i get this when requesting a location with a .htaccess contening my own directives (no problem if directives are in httpd.conf). Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 28586)] 0x0807d141 in perl_section_h

Re: Apache custom directives problem

2004-05-08 Thread Stas Bekman
Anthony Hinsinger wrote: Hello, i'm currently writing a mod_perl authentification handler, and i want to add apache custom directives. I followed techniques explained in the mod_perl cookbook (http://www.modperlcookbook.org/chapters/ch07.pdf) using Apache::Extutils::command_table() to add 2 dir