-
Notifications
You must be signed in to change notification settings - Fork 28
Bug report
Since GenomicsDB is a project under development, we do expect bugs to show up from time to time.
Please do go through the common issues wiki page before filing a bug report.
See the build wiki page for details on building TileDB/GenomicsDB. Omit the OPENMP=1 and BUILD=release parameters - instead add the parameter BUILD=debug. Typically, the following commands should be adequate
make clean-all
make BUILD=debug <other build options - Java, libcsv etc>
A core dump file contains the state of the program at the time of the crash and can be used to debug the program offline, even on a different machine, without any input data.
However, on most systems, core dump generation is disabled by default. You can find out how to enable generation of core dump files on the web; for example, "Enable Linux Core Dump" and "HOWTO enable core-dumps" for GNU/Linux and "Generating core dumps in el capitan " for MacOSX.
Ultimately, if you run ulimit -c, you should see a non-zero value (or the string unlimited).
Run your program; when it crashes/aborts, the system will produce a core dump file. Generally, the core dump file is created in the program working directory and is named core.<pid>
Compress the core dump file with gzip.
WARNING: the core dump contains program state at the time of the crash - this means that it will contain a small amount of the original data (from the TileDB/GenomicsDB array or VCF files). It is YOUR RESPONSIBILITY to ascertain that uploading core dump files to the public GenomicsDB Github repo isn't a violation of your institute policies and regulations.
Create an issue on Github and provide the following information:
- System type: GNU/Linux or MacOSX
- Description of the error
- Label the issue as a bug
- The git commit id of the GenomicsDB source used
Attach the following to the Github issue:
- The exact executable/library binary used to produce the core dump file (compress with gzip first)
- The gzip compressed core dump file
WARNING: the core dump contains program state at the time of the crash - this means that it will contain a small amount of the original data (from the TileDB/GenomicsDB array or VCF files). It is YOUR RESPONSIBILITY to ascertain that uploading core dump files to the public GenomicsDB Github repo isn't a violation of your institute policies and regulations.
- Overview of GenomicsDB
- Compiling GenomicsDB
-
Importing variant data into GenomicsDB
- Create a TileDB workspace
- Importing data from VCFs/gVCFs into TileDB/GenomicsDB
- Importing data from CSVs into TileDB/GenomicsDB
- Incremental import into TileDB/GenomicsDB
- Overlapping variant calls in a sample
- Java interface for importing VCF/CSV files into TileDB/GenomicsDB
- Dealing with multiple GenomicsDB partitions
- Querying GenomicsDB
- HDFS or S3 or GCS support in GenomicsDB
- MPI with GenomicsDB
- GenomicsDB utilities
- Try out with Docker
- Common issues
- Bug report
- External Contributions