[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Linphone-developers] Crash on new config using C-API
From: |
Florian Schröder |
Subject: |
[Linphone-developers] Crash on new config using C-API |
Date: |
Tue, 26 Apr 2016 10:46:41 +0200 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 |
Hi everyone,
I stumble over a strange behavior when creating a config and receiving a
call. This snipped is part of my initialization using the C-API:
static const char *config_path{"lp.conf"};
static const char *defaults_path{"lp.default.conf"};
auto config = lp_config_new_with_factory(config_path, defaults_path);
vtable.call_state_changed = call_state_changed;
vtable.text_received = text_received;
lc = linphone_core_new_with_config(&vtable, config, &userdata);
lp_config_unref(config);
When I start the program and lp.conf is not present, it aborts with the
error message 'double free or corruption' as soon as a call is incoming
(I auto accept all calls). When lp.conf is present, even if it is just
an empty file, everything is perfectly fine. The file is writable, even
if the program crashes, the lp.conf is written to file.
I can circumvent this by creating the file upfront, but I guess the
behavior is not right.
So my question is, should this work when lp.conf is not present or does
lp_config_new_with_factory assume to always receive existing file paths.
Thanks a lot
Florian
P.S.: OpenSUSE (Tumbleweed), gcc 5.3.1 (using c++14), linphone 3.9.1
(from repo)
- [Linphone-developers] Crash on new config using C-API,
Florian Schröder <=