Re: Apache custom directives problem

[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  0x0807c99b in perl_cmd_perl_TAKE1 (cmd=0xbffffa10, data=0xbffffa10,
    one=0xbffffa10 "[EMAIL PROTECTED]") at perl_config.c:859
invoked by

#3  0x080b9fe9 in invoke_cmd (cmd=0x4001bc80, parms=0xbffffa10,
    mconfig=0x888fdb4, args=0xbfffd9e3 "") at http_config.c:828
You can test, by going to frame #2

gdb> up
gdb> up
gdb> p data->obj
gdb> p *data->obj
So most likely something is wrong with your XS code that creates the new 
directive. Show us the XS code.

--
__________________________________________________________________
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
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html