[AOLSERVER] URL handling produce segfault
Alexey Pechnikov
http://localhost:8100/json/object/search/?q=%D1%82%D0%B0%D0%B2%D1%80*+2010
2. It's fail:
http://localhost:8100/json/object/search/?q=%D1%82%D0%B0%D0%B2%D1%80*+2011
AOL Log:
[-default:0-] Fatal: received fatal signal 11
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <list...@listserv.aol.com> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
Gustaf Neumann
both URLs work nicely for me (using 4.5.1 from sourceforge under
Mac OS X); the URLs are rewritten finally into
..../?q=тавр*+2011
Can it be that you have some unusual encoding settings?
-gustaf neumann
On 04.07.11 11:54, Alexey Pechnikov wrote:
> 1. It's work fine:
> http://localhost:8100/json/object/search/?q=%D1%82%D0%B0%D0%B2%D1%80*+2010
>
> 2. It's fail:
>
> http://localhost:8100/json/object/search/?q=%D1%82%D0%B0%D0%B2%D1%80*+2011
>
> AOL Log:
> [-default:0-] Fatal: received fatal signal 11
>
>
--
Alexey Pechnikov
(full-text search extension for SQLite3 with Snowball stemmer support).
Is it possible to prevent (or detailed logging) the AOL segfault in case
of tcl extension segfault? I use runit supervisor and AOL is restarting
automatically but debugging in this situation is not easy.
--
Best regards, Alexey Pechnikov.
http://pechnikov.tel/
Gustaf Neumann
whether is happens in aolserver, in tcl or in an extension.
you might have a chance to recover from segfaults in
nsproxy, but certainly, the best approach is to get rid of
these... -gn
On 05.07.11 21:25, Alexey Pechnikov wrote:
> Is it possible to prevent (or detailed logging) the AOL segfault in case
> of tcl extension segfault? I use runit supervisor and AOL is restarting
> automatically but debugging in this situation is not easy.
>
--