On 3 June 2011 10:16, Daniel-Constantin Mierla wrote:
>>> Sorry for disturbing... is there any chance?
>>
>> it is, but I cannot promise a date yet -- too many things to catch up,
>> while testing this is very inconvenient not having a way to troubleshoot.
>
> Not to forget about this one, is
On 5/19/11 9:45 AM, Daniel-Constantin Mierla wrote:
On 5/18/11 8:29 AM, Roman Yeryomin wrote:
On 2 May 2011 15:47, Daniel-Constantin Mierla wrote:
On 5/1/11 11:51 PM, Roman Yeryomin wrote:
On 27 April 2011 20:19, Roman Yeryomin
wrote:
On 27 April 2011 17:26, Daniel-Constantin Mierla
On 5/18/11 8:29 AM, Roman Yeryomin wrote:
On 2 May 2011 15:47, Daniel-Constantin Mierla wrote:
On 5/1/11 11:51 PM, Roman Yeryomin wrote:
On 27 April 2011 20:19, Roman Yeryominwrote:
On 27 April 2011 17:26, Daniel-Constantin Mierla
wrote:
Can you try with tcp disabled? i.e.,
disable
On 2 May 2011 15:47, Daniel-Constantin Mierla wrote:
>
>
> On 5/1/11 11:51 PM, Roman Yeryomin wrote:
>>
>> On 27 April 2011 20:19, Roman Yeryomin wrote:
>>>
>>> On 27 April 2011 17:26, Daniel-Constantin Mierla
>>> wrote:
Can you try with tcp disabled? i.e.,
disable_tcp=yes
>>
On 2 May 2011 17:01, Roman Yeryomin wrote:
> On 2 May 2011 15:47, Daniel-Constantin Mierla wrote:
>>
>>
>> On 5/1/11 11:51 PM, Roman Yeryomin wrote:
>>>
>>> On 27 April 2011 20:19, Roman Yeryomin wrote:
On 27 April 2011 17:26, Daniel-Constantin Mierla
wrote:
>
> Can you t
On 2 May 2011 15:47, Daniel-Constantin Mierla wrote:
>
>
> On 5/1/11 11:51 PM, Roman Yeryomin wrote:
>>
>> On 27 April 2011 20:19, Roman Yeryomin wrote:
>>>
>>> On 27 April 2011 17:26, Daniel-Constantin Mierla
>>> wrote:
Can you try with tcp disabled? i.e.,
disable_tcp=yes
>>
On 5/1/11 11:51 PM, Roman Yeryomin wrote:
On 27 April 2011 20:19, Roman Yeryomin wrote:
On 27 April 2011 17:26, Daniel-Constantin Mierla wrote:
Can you try with tcp disabled? i.e.,
disable_tcp=yes
in your config file.
Might be the way the module is initialized for tcp handling.
it segf
On 27 April 2011 20:19, Roman Yeryomin wrote:
> On 27 April 2011 17:26, Daniel-Constantin Mierla wrote:
>> Can you try with tcp disabled? i.e.,
>>
>> disable_tcp=yes
>>
>> in your config file.
>>
>> Might be the way the module is initialized for tcp handling.
>>
>
> it segfaults anyway - see new
Can you try with tcp disabled? i.e.,
disable_tcp=yes
in your config file.
Might be the way the module is initialized for tcp handling.
Cheers,
Daniel
On 4/26/11 4:05 PM, Roman Yeryomin wrote:
On 26 April 2011 11:58, Daniel-Constantin Mierla wrote:
On 4/21/11 2:21 PM, Roman Yeryomin wrote:
On 4/21/11 2:21 PM, Roman Yeryomin wrote:
On 21 April 2011 12:16, Daniel-Constantin Mierla wrote:
(gdb) bt full
#0 0xb7228e3a in parseurl (url=0xb7213230 "T�0\b#") at perlvdbfunc.c:60
No locals.
#1 0xb7228e7d in perlvdb_db_init (url=0x1
Seems that the db url is not passed properly.
While y
On 21 April 2011 12:16, Daniel-Constantin Mierla wrote:
>> (gdb) bt full
>> #0 0xb7228e3a in parseurl (url=0xb7213230 "T�0\b#") at perlvdbfunc.c:60
>> No locals.
>> #1 0xb7228e7d in perlvdb_db_init (url=0x1
> Seems that the db url is not passed properly.
>
> While you are in gdb, do:
>
> frame 2
On 4/20/11 5:07 PM, Roman Yeryomin wrote:
On 20 April 2011 15:24, Daniel-Constantin Mierla wrote:
On 4/20/11 1:54 PM, Roman Yeryomin wrote:
On 19 April 2011 13:12, Roman Yeryominwrote:
ok, here is the backtrace:
# gdb kamailio core
...
Reading symbols from /usr/local/lib/kamailio/modul
On 20 April 2011 15:24, Daniel-Constantin Mierla wrote:
> On 4/20/11 1:54 PM, Roman Yeryomin wrote:
>>
>> On 19 April 2011 13:12, Roman Yeryomin wrote:
>>>
>>> ok, here is the backtrace:
>>>
>>> # gdb kamailio core
>>> ...
>>> Reading symbols from /usr/local/lib/kamailio/modules_k/perlvdb.so...do
On 4/20/11 1:54 PM, Roman Yeryomin wrote:
On 19 April 2011 13:12, Roman Yeryomin wrote:
ok, here is the backtrace:
# gdb kamailio core
...
Reading symbols from /usr/local/lib/kamailio/modules_k/perlvdb.so...done.
Loaded symbols for /usr/local/lib/kamailio/modules_k/perlvdb.so
...
Core was ge
On 19 April 2011 13:12, Roman Yeryomin wrote:
>
> ok, here is the backtrace:
>
> # gdb kamailio core
> ...
> Reading symbols from /usr/local/lib/kamailio/modules_k/perlvdb.so...done.
> Loaded symbols for /usr/local/lib/kamailio/modules_k/perlvdb.so
> ...
> Core was generated by `kamailio -'.
>
On 18 April 2011 15:47, Henning Westerholt wrote:
> On Monday 18 April 2011, Roman Yeryomin wrote:
>> coredump? easy :)
>> you can pick core file itself here (it's pretty heavy to send to the list):
>> http://83.99.159.113/core.kamailio.20110418-1331
>>
>> What do you mean by backtrace? log output
On Monday 18 April 2011, Roman Yeryomin wrote:
> coredump? easy :)
> you can pick core file itself here (it's pretty heavy to send to the list):
> http://83.99.159.113/core.kamailio.20110418-1331
>
> What do you mean by backtrace? log output or strace output?
Hi Roman,
he refers to a gdb backtra
On 18 April 2011 12:52, Daniel-Constantin Mierla wrote:
> Hello,
>
> On 4/18/11 11:28 AM, Roman Yeryomin wrote:
>>
>> Hi!
>>
>> I'm trying to use perlvdb module but seems that it's not working.
>> Seems that needed functions are not exported correctly:
>>
>> kamailio[11525]: ERROR: [db.c:79]: mod
Hello,
On 4/18/11 11:28 AM, Roman Yeryomin wrote:
Hi!
I'm trying to use perlvdb module but seems that it's not working.
Seems that needed functions are not exported correctly:
kamailio[11525]: ERROR: [db.c:79]: module db_perlvdb does not
export db_use_table function
Looking at perlvdb.c one
Hi!
I'm trying to use perlvdb module but seems that it's not working.
Seems that needed functions are not exported correctly:
kamailio[11525]: ERROR: [db.c:79]: module db_perlvdb does not
export db_use_table function
Looking at perlvdb.c one can see that module exports it's functions as
"perlvd
20 matches
Mail list logo
