segfault at 10 ip 00007fbb33028d4e sp 00007ffd8d3bf380 error 4 in libdbus-1.so.3.19.13[7fbb33027000+2e000]
Srinadh Penugonda
srinadh0 at yahoo.com
Wed Sep 29 03:14:32 UTC 2021
Thats what I suspect too but I could not understand what is the issue.
Based on the below interface (which I acquired through busctl),root at sonic:~# busctl introspect org.SONiC.HostService.keyhandler /org/SONiC/HostService/keyhandler
NAME TYPE SIGNATURE RESULT/VALUE FLAGS
org.SONiC.HostService.keyhandler interface - - -
.key_ctl method as is -
dbusxx-xml2cpp generated the proxy header with the below signature for key_ctl
::DBus::Struct< int32_t, std::string > key_ctl(const std::vector< std::string >& data)
And, that is exactly what I am sending - a vector of strings - from HostQuery(): vector<string> vals = {"pwEncrypt","eventd"};
syslog(LOG_CRIT, "calling key_ctl"); ret = host_client.key_ctl(vals); syslog(LOG_CRIT, "key_ctl returned");
~~ Thanks, Srinadh
On Tuesday, September 28, 2021, 06:41:55 PM PDT, Lawrence D'Oliveiro <ldo at geek-central.gen.nz> wrote:
On Wed, 29 Sep 2021 01:39:25 +0000 (UTC), Srinadh Penugonda wrote:
> If it crashes in the host module, I should see it in the backtrace.
> But the backtrace is pointing to libdbus..
Very likely because the C++ code is passing some bad structure to
libdbus.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/dbus/attachments/20210929/3946ffbe/attachment-0001.htm>
More information about the dbus
mailing list