It always generate coredump for otgc client

[JiangJohnny]

Hi dears,
When I was trying the otgc client, It always generated coredump both ogtc linux version on ubuntu 18.04(and 16.04) and android version on MiPhone8 (android 7.1.1).
Here is the log from ubuntu when run otgc.sh. I tried on many laptops and got the same error.
I appreciate if you could take time to look at it. Thanks.

johnny@johnny-Latitude-E7450:$ otgc.sh
2018-11-09 13:42:26 DEBUG App:58 - Starting the application
2018-11-09 13:42:26 DEBUG logging:38 - Logging Provider: org.jboss.logging.Log4jLoggerProvider
2018-11-09 13:42:26 INFO LogHelper:31 - HHH000204: Processing PersistenceUnitInfo [
name: otgc-pu
...]
2018-11-09 13:42:26 INFO Version:46 - HHH000412: Hibernate Core {5.3.2.Final}
2018-11-09 13:42:26 INFO Environment:213 - HHH000206: hibernate.properties not found
2018-11-09 13:42:26 INFO Version:49 - HCANN000001: Hibernate Commons Annotations {5.0.4.Final}
2018-11-09 13:42:27 WARN pooling:73 - HHH10001002: Using Hibernate built-in connection pool (not for production use!)
2018-11-09 13:42:27 INFO pooling:129 - HHH10001005: using driver [org.hsqldb.jdbcDriver] at URL [jdbc:hsqldb:file:db/otgc-pu;create=true;]
2018-11-09 13:42:27 INFO pooling:138 - HHH10001001: Connection properties: {user=root, password=****, charSet=UTF-8}
2018-11-09 13:42:27 INFO pooling:143 - HHH10001003: Autocommit mode: false
2018-11-09 13:42:27 INFO DriverManagerConnectionProviderImpl:281 - HHH000115: Hibernate connection pool size: 20 (min=1)
2018-11-09 13:42:27 INFO ENGINE:? - checkpointClose start
2018-11-09 13:42:27 INFO ENGINE:? - checkpointClose synched
2018-11-09 13:42:27 INFO ENGINE:? - checkpointClose script done
2018-11-09 13:42:27 INFO ENGINE:? - checkpointClose end
2018-11-09 13:42:27 INFO Dialect:157 - HHH000400: Using dialect: org.hibernate.dialect.HSQLDialect
Hibernate: alter table HOSTS drop constraint FKhqk00yqb37tvb65wa27v2nawj
2018-11-09 13:42:28 INFO access:47 - HHH10001501: Connection obtained from JdbcConnectionAccess [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess@720773bd] for (non-JTA) DDL execution was not in auto-commit mode; the Connection 'local transaction' will be committed and the Connection will be set into auto-commit mode.
Hibernate: drop table DEVICES if exists
Hibernate: drop table HOSTS if exists
Hibernate: create table DEVICES (deviceid varchar(255) not null, name varchar(255), primary key (deviceid))
2018-11-09 13:42:28 INFO access:47 - HHH10001501: Connection obtained from JdbcConnectionAccess [org.hibernate.engine.jdbc.env.internal.JdbcEnvironmentInitiator$ConnectionProviderJdbcConnectionAccess@47d55f4c] for (non-JTA) DDL execution was not in auto-commit mode; the Connection 'local transaction' will be committed and the Connection will be set into auto-commit mode.
Hibernate: create table HOSTS (id varchar(255) not null, host varchar(255))
Hibernate: alter table HOSTS add constraint FKhqk00yqb37tvb65wa27v2nawj foreign key (id) references DEVICES
2018-11-09 13:42:28 INFO SchemaCreatorImpl:489 - HHH000476: Executing import script 'org.hibernate.tool.schema.internal.exec.ScriptSourceInputNonExistentImpl@335a025d'
2018-11-09 13:42:28 INFO QueryTranslatorFactoryInitiator:47 - HHH000397: Using ASTQueryTranslatorFactory
2018-11-09 13:42:28 DEBUG ProvisionRepository:87 - initOICStack
2018-11-09 13:42:28 DEBUG ProvisionRepository:118 - Sql db directory exists at //usr/share/otgc/./db/
Hibernate: select deviceenti0_.deviceid as deviceid1_0_, deviceenti0_.name as name2_0_ from DEVICES deviceenti0_ where deviceid=?
Hibernate: select deviceenti0_.deviceid as deviceid1_0_0_, deviceenti0_.name as name2_0_0_ from DEVICES deviceenti0_ where deviceenti0_.deviceid=?
terminate called after throwing an instance of 'std::logic_error'
what(): basic_string::_M_construct null not valid
/usr/bin/otgc.sh: line 6: 4099 Aborted (core dumped) java -jar /usr/lib/otgc/otgc-1.2.0-jfx.jar
johnny@johnny-Latitude-E7450:$

[javiguerra]

Hello,
We think that the problem could be a bug we have found on IoTivity when OTGC client scans devices, but could you say us if there are another OCF device, the CTT or Device Spy on the same network?
Thanks

[JiangJohnny]

Hi Javiguerra,
Thanks for your comments. There were only one server runs on raspberry pi 3, and one OTGC client in the network. It didn't work yet if I stopped the OCF server. But it works after change to another Wi-Fi router. It might not support IPv6 on the previous router. Is this the problem?

[dbartolomea]

Hi @JiangJohnny
This could be the reason as we have identified some random issues with routers not handling properly IPv6 IoTivity communications. Anyway, we will continue investigating. Thanks for reporting.

[WAvdBeek]

This should be solved with the newer versions of OTGC