temporal modules: segmentation fault

[veroandreo]

[from grass-dev ML, just not to loose track of this]

I get "segmentation fault" when running temporal commands, i.e., G7:t.list, G7:t.info, G7:t.create, G7:t.register (haven't tested them all).

The command works as expected, but I get the "Segmentation fault (core dumped)" whenever I run any temporal module.

I use grass trunk r73007 in Fedora 28.

strace output:

strace t.info LST_Day_monthly
[...]
stat("/home/veroandreo/grassdata/nc_spm_08_grass7/modis_lst/tgis/sqlite.db", {st_mode=S_IFREG|0644, st_size=585728, ...}) = 0
close(3)                                = 0
getpid()                                = 7519
wait4(7527, 0x7fff654f8644, WNOHANG, NULL) = 0
write(5, "\0\0\0\17\200\2]q\1U\4STOPq\2a.", 19) = 19
getpid()                                = 7519
wait4(7527, 0x7fff654f83d4, WNOHANG, NULL) = 0
select(0, NULL, NULL, NULL, {tv_sec=0, tv_usec=1000}) = ? ERESTARTNOHAND (To be restarted if no handler)
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_EXITED, si_pid=7527, si_uid=1000, si_status=1, si_utime=0, si_stime=0} ---
select(0, NULL, NULL, NULL, {tv_sec=0, tv_usec=0}) = 0 (Timeout)
wait4(7527, [{WIFEXITED(s) && WEXITSTATUS(s) == 1}], WNOHANG, NULL) = 7527
close(5)                                = 0
futex(0x55b0471463a0, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 0, NULL, 0xffffffff) = 0
getpid()                                = 7519
wait4(7528, 0x7fff654f8644, WNOHANG, NULL) = 0
write(7, "\0\0\0\t\200\2]q\1K\0a.", 13) = 13
kill(7528, SIGTERM)                     = 0
close(7)                                = 0
wait4(7528, 0x7fff654f8644, WNOHANG, NULL) = 0
kill(7528, SIGTERM)                     = 0
wait4(7528, 0x7fff654f8644, WNOHANG, NULL) = 0
getpid()                                = 7519
wait4(7528, [{WIFSIGNALED(s) && WTERMSIG(s) == SIGTERM}], 0, NULL) = 7528
--- SIGCHLD {si_signo=SIGCHLD, si_code=CLD_KILLED, si_pid=7528, si_uid=1000, si_status=SIGTERM, si_utime=0, si_stime=0} ---
rt_sigaction(SIGINT, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f78a8694fc0}, {sa_handler=0x7f78a8a2c880, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x7f78a8694fc0}, 8) = 0
munmap(0x7f78a8f16000, 32)              = 0
close(9)                                = 0
munmap(0x7f78a8f17000, 32)              = 0
close(6)                                = 0
close(8)                                = 0
futex(0x7f7897973574, FUTEX_WAKE_PRIVATE, 2147483647) = 0
futex(0x7f78966421e4, FUTEX_WAKE_PRIVATE, 2147483647) = 0
munmap(0x7f787bda5000, 33554496)        = 0
munmap(0x7f7879da4000, 33554496)        = 0
munmap(0x7f7877da3000, 33554496)        = 0
munmap(0x7f7875da2000, 33554496)        = 0
munmap(0x7f7873da1000, 33554496)        = 0
munmap(0x7f7871da0000, 33554496)        = 0
munmap(0x7f786fd9f000, 33554496)        = 0
munmap(0x7f786dd9e000, 33554496)        = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0x7f787bda5008} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)

The thread is here: ​https://lists.osgeo.org/pipermail/grass-dev/2018-July/089157.html

[neteler]

The bug occurred indeed in the package openblas-openmp. It had been solved today in Fedora, see

​https://bugzilla.redhat.com/show_bug.cgi?id=1605231

and was no GRASS GIS bug.