Closed #716.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/716#event-749851763___
sr-dev mailing list
sr-dev@lists.sip-router.org
http:
OK, thanks for testing and reporting back. Open a new item when you get the
segfault.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/716#issuecomment-238555854
I just tried your patch, it seems to work.
I'm trying to reproduce the segfault, for now, without success, i'll tell you.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/716#issueco
Thank you, i'll try your patch.
For the coredump, i tried to use gdb but it didn't help as kamailio exists
normally...
The only informations i have at "crash" are the textual information about
threads memory status at "crash" moment.
I'll send you these informations, you'll see what i mean...
I pushed a patch to master branch to avoid the comma at the end of header --
can you give it a try?
For the segmentation fault, can you get the backtrace with gdb from the
coredump file?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view i
You're welcome.
After more tries, the segmentation faults don't seem to be related to my patch
as :
- the segmentation occurs between the database locks release and the
"tps_reappend_route" function and simply adding a sleep between database locks
releases and it solved (partially) my issue.
-
Thanks for tracking this down -- I will see how can be fixed and push the
commit for it.
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/716#issuecomment-236972605_
After more debugging, it seems that the Route header is not well regenerated
from topos stored values.
There is a wrong additional comma at the end of the `Route` header:
`,`
Instead of
``
I tried to reduce sb size by replacing last character with \0, that makes it
work
`*(sb.s-1)='\0';`
b
I made some more debug by adding some more loggin in topos_mod.c and parser
modules, it seems that some empty lines are added to the Record-Route header,
and so, parsing fails.
More precisely it seems that topos use internal headers and zeroes them instead
of deleting the lines after usage.
Th
Thank you for your reply, please find the debug log attached to this message.
parse_rr error happens first at line 5287
note that the same configuration, without topos, works like a charm
[topos-debug.txt](https://github.com/kamailio/kamailio/files/371745/topos-debug.txt)
---
You are receiving
Can you run with debug=3 and attach all the logs printed by kamailio when the
error is printed?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/kamailio/kamailio/issues/716#issuecomment-233640691__
On a setup i made, when using record_route without topos, the dialogs are well
followed
The same setup with topos activated leads to parse_rr() errors like this one:
ERROR: [parser/parse_rr.c:119]: do_parse_rr_body(): parse_rr(): Text
after comma missing
I made some SQL captures to see more a
12 matches
Mail list logo
