Re: segfault on xpath queries :P

darryl wrote:
> 
>>>
>>> Ok... well, I ended up using all client-side xslt & xpath for the 
>>> demo I had to do on Saturday. I will try to do some more debugging, 
>>> but since I can't reproduce this behaviour when I'm driving libxml 
>>> directly, I may just start using the libraries themselves.
>>> -- 
>>>
>> It's unfortunate but it appears Kimbro is otherwise occupied. I 
>> looked, but dont' know the code well enough to do some serious debugging.
>> Hopefully you can see something in your debugging attempts.
>>
>> cheers,
>> darryl
>>
> FWIW, i don't know shit about debugging python extension modules in 
> python BUT when i ran python under gdb and ran the script i got:
>  >>> from Weblog import Weblog
>  >>> blog = Weblog('.')
> Registering prefix syncato
>  >>> blog.handleRequest('//character','','','')
> 
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 16384 (LWP 6013)]
> 0x40d49980 in xmlReconciliateNs () from /usr/lib/libxml2.so.2
> (gdb)
> 
> 
> -darryl
> 

It seems to by crashing on this function call:

result.reconciliateNs(doc.getDocument())

It also seems to only affect 501.xml,503.xml and 504.xml

-darryl

-- 
http://randomthoughts.vandorp.ca/WK/blog


-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
deliver higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3