23 Jul
2019
23 Jul
'19
5:29 p.m.
Hello Henning,
Thanks for your help. I test both -D and -DD option when running kamailio
in gdb.
When running kamailio with -D it doesn't accept any request on TCP, and
when I run with -DD option gdb doesn't stop on the break point.
In summary:
$ sudo gdb kamailio
(gdb) b isc_from_as
(gdb) r -f /path/to/kamailio.cfg -D ---> doesn't accept TCP requests
(gdb) r -f /path/to/kamailio.cfg -DD ----> gdb doesn't stop on break point
Regards,
Ali
On Tue, Jul 23, 2019 at 9:12 PM Henning Westerholt <hw(a)skalatan.de> wrote:
(adding sr-dev to CC)
Hello Ali,
have a look to the kamailio binary parameter and the children parameter in
configuration. You can actually start kamailio with (almost) no forking.
You will get a lot of debugging information if you enable the kamailio
debugging in the cfg.
If you want to debug only the internals of the core or a specific Kamailio
module, there is also a debugger module available that can be useful to
debug only certain parts of the server. You can also set breakpoints at
certain points in the cfg, or dump internal state with it.
Cheers,
Henning
Am 23.07.19 um 11:39 schrieb Ali Shirvani:
Hi all,
I want to trace function calls in a kamailio module, e.g. ims_isc module.
I installed kamailio-dbg package and started the kamailio with gdb: `gdb
kamailio` I also set break point on target function, but it seems gdb
doesn't stop on that break point.
How should I start gdb and set break points? it seems gdb couldn't handle
kamailio child processes that forked in start.
Regards,
Ali
_______________________________________________
Kamailio (SER) - Users Mailing
Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
--
Henning Westerholt - https://skalatan.de/blog/
Kamailio services - https://skalatan.de/services