Hello list,
I'm trying to debug my module after it crashed by SIGSEGV, but the problem
is that I'm unable to see the relevant data in the core file that's being
dumped after the crash.
For example, if I do *bt full, *I get:
0 0x0ef0f494 in append_string () from
/opt/install/kamailio-3.2.3/lib/kamailio/modules_k/cnx3a.so
No symbol table info available.
#1 0x0eef9658 in build_message () from
/opt/install/kamailio-3.2.3/lib/kamailio/modules_k/cnx3a.so
No symbol table info available.
Backtrace stopped: frame did not save the PC
Only the functions that were called but no parameter values.
AFAIK, if I compile kamailio from sources, it is by default compiled with
the -g option, so, it looks like that I'm missing something else.
Regards.
Carlos.
Hello,
I am curious what others are doing in the following scenario.
I am attempting to fix on the proxy side the effects of a broken UA.
Essentially the problem is the UA is not sending Route headers (per
record-routing) in its ACK.
What I am looking to do is "correct" this on the proxy, so when the ACK is
routed back to us, we simply fix the packet and relay it back upstream.
I was looking into dlg_get() however it does not appear to restore route
headers, etc.
Looking for any suggestions on how to accomplish this.
Sincerely,
Brandon Armstead
Am Mittwoch, 5. September 2012, 14:06:14 schrieb Vieri:
> > > # FOREVER="2020-05-28 21:32:15"
> > > [..]
> >
> > this definitions just needs to be the same as in the
> > database scheme, as they
> > are used in the script. The path was indeed outdated, I've
> > just fixed it in git
> > master.
>
> Why is the default FOREVER="2020-05-28 21:32:15"?
> I suppose it's just the way the original dev set it up.
> Could the package default be something more like the following?
> FOREVER="9999-01-01 00:00:00"
Hello Vieri,
well, there is the issue that this is then wrongly parsed from some databases,
also depending on the exact type which is used. In mysql it supports in some
types a date like this, in some types only to the year 2038.
But you're right in bringing this issue up. I'd suggest to update it to
"2030-05-28 21:32:15" or something like this.
Cheers,
Henning Westerholt
Hi, I've experimented column size isues (too small) when trying to
store a double Path header in the location table. It seems that
current size is:
lib/srdb1/schema/location.xml:
<column>
<name>path</name>
<type>string</type>
<size>&uri_len;</size>
<null/>
<default><null/></default>
<description>Path Header(s) per RFC 3327</description>
</column>
It seems to become 128 which is not enough at all for two Path headers
if the URI's contain parameters.
Is it ok if I increase it to 512? any other file to touch?
Thanks a lot.
--
Iñaki Baz Castillo
<ibc(a)aliax.net>