Displaying 7 results from an estimated 7 matches for "client_dict_lookup".
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...> > > >>>>>> performed by doveadm. Indeed the client gets the proper string from the
> > > >>>>>> socket and to my surprise, it is properly unescaped.
> > > >>>>>>
> > > >>>>>> Then, in "client_dict_lookup" ("lib-dict/dict-client.c"), the call to
> > > >>>>>> "p_strdup" returns an empty string (null byte set at the target address).
> > > >>>>>>
> > > >>>>>> Before the call to the dict "->...
2016 Oct 16
2
Dict proxy client returning empty string instead of multiline string
...uot;\1r" and "\1n" are the escape sequences used by
"lib/strescape.c". I went deeped and debugged the call to "dict_lookup"
performed by doveadm. Indeed the client gets the proper string from the
socket and to my surprise, it is properly unescaped.
Then, in "client_dict_lookup" ("lib-dict/dict-client.c"), the call to
"p_strdup" returns an empty string (null byte set at the target address).
Before the call to the dict "->lookup" attribute (client_dict_lookup):
RAX: 0x7ffff73a37c0 (push r14)
RBX: 0x6831b8 ("priv/reply_bo...
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...gt;>
> >> Okay, it seems to me that the bug is due to "t_str_tabunescape" using
> >> the unsafe datastack ("t_strdup_noconst") while the string is actually
> >> returned in an async callback.
> >>
> >> Before it is handled by "client_dict_lookup", "client_dict_wait"
> >> actually fires some IO loops that are more than likely to call "t_pop"
> >> and free/flush the result string (I checked, it does call "t_pop" a
> >> couple times indeed). Maybe it would be safer to use a standar...
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...cape sequences used by
>> "lib/strescape.c". I went deeped and debugged the call to "dict_lookup"
>> performed by doveadm. Indeed the client gets the proper string from the
>> socket and to my surprise, it is properly unescaped.
>>
>> Then, in "client_dict_lookup" ("lib-dict/dict-client.c"), the call to
>> "p_strdup" returns an empty string (null byte set at the target address).
>>
>> Before the call to the dict "->lookup" attribute (client_dict_lookup):
>>
>> RAX: 0x7ffff73a37c0 (push...
2016 Oct 17
2
Dict proxy client returning empty string instead of multiline string
...Jaury <pierre at jaury.eu> wrote:
>
>
> Okay, it seems to me that the bug is due to "t_str_tabunescape" using
> the unsafe datastack ("t_strdup_noconst") while the string is actually
> returned in an async callback.
>
> Before it is handled by "client_dict_lookup", "client_dict_wait"
> actually fires some IO loops that are more than likely to call "t_pop"
> and free/flush the result string (I checked, it does call "t_pop" a
> couple times indeed). Maybe it would be safer to use a standard
> datastack pool when...
2016 Oct 17
1
Dict proxy client returning empty string instead of multiline string
...by
>>> "lib/strescape.c". I went deeped and debugged the call to "dict_lookup"
>>> performed by doveadm. Indeed the client gets the proper string from the
>>> socket and to my surprise, it is properly unescaped.
>>>
>>> Then, in "client_dict_lookup" ("lib-dict/dict-client.c"), the call to
>>> "p_strdup" returns an empty string (null byte set at the target address).
>>>
>>> Before the call to the dict "->lookup" attribute (client_dict_lookup):
>>>
>>> RAX: 0x...
2008 Mar 29
3
Expire plugin with Mysql
Hey guys, got a question about the expire plugin. According to the
wiki, the expire plugin "keeps an internal database (Berkeley DB or
SQL)". I was wondering what fields in the mysql table are needed for
expire to work.
I assume it is setup is similar to the quota dict
setup, so was just wondering what fields are required (i.e:
select_field, where_field, username_field, for quota).