InplaceIndexTest cored on latest master

Environment

Any

Description

The problem can reproduce on the latest master with:

/opt/HPCCSystems/bin/unittests InplaceIndexTest Segmentation fault (core dumped)

Unfortunately when I tried to check the core file with GBD (8.1.1), it crashed with internal error. 

gdb /opt/HPCCSystems/bin/unittests ./core_unittests.17145 GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law.  Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". ... Reading symbols from /opt/HPCCSystems/bin/unittests...done. [New LWP 17145] [New LWP 17146] [New LWP 17147] [New LWP 17149] [New LWP 17148] [New LWP 17150] [New LWP 17151] [New LWP 17152] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". /build/gdb-veKdC1/gdb-8.1.1/gdb/symfile.c:944: internal-error: sect_index_text not initialised A problem internal to GDB has been detected, further debugging may prove unreliable. Quit this debugging session? (y or n)

any idea?

Conclusion

A test for new code, but I will debug and release a fix

Activity

Show:

Attila Vamos April 14, 2023 at 5:10 PM

It seems there were two problems: 

  1. Both my local system and OBT, there is different version of platform built and installed into the same directory (/opt/HPCCSystems/) and somehow (perhaps a bug in the package uninstall code I will investigate) a couple of old libraries (libRembed.so, libazurefile.so) left behind and that caused the crash and core file generation. 

  1. At the end of the void testSearching() (unit test method in system/jhtree/jhinplace.cpp) there is an exit(0) statement which causes the unit test terminates without correct finalization and report. 

  

The 1. should resolve in the test systems, for the second I will release a fix soon. 

 

Gavin Halliday March 8, 2023 at 2:37 PM

As far as I can tell this is a build problem, rather than a problem with the new code. It still needs investigating, but will not prevent the 1st rc of 9.0.0

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Affects versions

Created March 8, 2023 at 11:32 AM
Updated April 17, 2023 at 10:45 AM
Resolved April 17, 2023 at 10:44 AM

Flag notifications