-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metabuli v1.0.0 segfault #10
Comments
With the official binary AVX2 binaries:
|
Even more strange things:
Running as myself (sjaenick), this works - file owned by myself: ... while this segfaults, even though the file is readable via its group (and world) permissions: Performing exactly the same using the |
Thank you for sharing the issue with great details! It will help us provide more stable software.
|
Thank you so much for the detailed issue description and experiments. I also tried to reproduce the issue as well but failed. Just to clarify, if you run metabuli under your own account it does not crash (at all), but if you use another user it crashes? |
It crashes both under my own account as well as with another one; the strange thing here is that for an input file readable by both accounts, the outcome reproducibly differs. Also, copying the input file to a different location makes a difference (and I have no idea what might cause this).
When executed under my own account, this segfaults in the metamer extraction step; when run under the |
EDIT: It still segfaults, even with more than one thread:
|
I have a testcase here: If the input file is writable (e.g. permissions 644), it works. Change it to https://github.com/steineggerlab/Metabuli/blob/master/src/commons/Classifier.cpp#L161 creates
the segfault during metamer extraction seems to be fixed. |
i think the second segfault (during 'Comparing qeury and reference metamers') might be due to a similar https://github.com/steineggerlab/Metabuli/blob/master/src/commons/Classifier.cpp#L485 creates a R/W mapping A readonly mapping, i.e. |
Hi there,
Metabuli looks very interesting, but I'm encountering segmentation faults at two different stages (see below).
Interestingly, I'm seeing three different outcomes for the same input data, and even just changing the location
of the input file seems to be sufficient to arrive at a different result (one of: 1. it just works 2. segfault in metamer
extraction, 3. segfault in metamer comparison).
Metabuli v.1.0.0 compiled from source (
-DCMAKE_BUILD_TYPE=Debug
), with your pre-built database obtained as permetabuli databases RefSeq refseq tmp
./vol/mgx-sw/bin/metabuli classify --seq-mode 1 xxxy.in /vol/biodb/local_databases/MGX/metabuli/refseq/ outdir jobid --threads 1 --max-ram 64
System is a Intel(R) Xeon(R) CPU E5-4627 with 1TB of memory, running Ubuntu 20.04.6 LTS.
Comparing qeury and reference metamers
stageI'm attaching the sample input file I've been using for this.
input.fas.txt
The text was updated successfully, but these errors were encountered: