Closed EricR86 closed 5 years ago
Original comment by Coby Viner (Bitbucket: cviner2, GitHub: cviner).
This was likely due to system-specific idiosyncrasies. It can no longer be directly tested in its original computing environment, which is now obsolete. It has yet to be re-encountered elsewhere, but no attempts have been made to assess this.
Original report (archived issue) by Coby Viner (Bitbucket: cviner2, GitHub: cviner).
The original report had attachments: core.19535.gz
One Genomedata run, out of multiple similar parallel runs, segfaulted, producing a core dump. This has also happened twice on a previous occasion, but I mis-attributed them to system-specific aberrations.
Inspection of the
core
file produced (and enclosed, gzipped), viafile
yields:/usr/bin/h5repack --version
yielded:h5repack: (Version 1.8.7)
.Execution of a
gdb
backtrace onh5repack
with this core file, yields the following stack trace:The segfaulting line occurs in
H5O_dec_rc
ofH5O.c
, and appears to be due to the deference of theoh
pointer, which contains0x0
(i.e. possibly set to, but functionally equivalent to,NULL
).I am currently attempting to determine if I can reconstruct the Genomedata run in question and if can find any pertinent log information.I was not able to find any clear sample that was impacted by this segmentation fault. All of the outputs appeared similar (yet only 1 of 32 had a core dump produced). I may be able to comment further after continuing with downstream analyses, but that does not appear likely to yield further insight into this error.