-
Notifications
You must be signed in to change notification settings - Fork 194
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
vg giraffe: unable to retrieve stacktrace.txt file because no access to /tmp #3882
Comments
The workaround for getting the traceback in situations like this is to set the We probably should make that the default, and also fix the traceback dump system to respect TMPDIR, maybe by pre-checking it at startup. |
@adamnovak Thank you for your suggestions!
What do you think may be causing it? |
It looks like I think, because the disassembly says we're near calling the funnel pass function with max_multimaps, that a call to one of the other process until threshold functions is optimized away and we are actually in here: Lines 2296 to 2362 in 915d3bc
I think we are probably at this line, where we copy the alignments: Line 2309 in 915d3bc
This does some fancy indexing, and it's possible there's a mistake in it. I think we can build with |
Thank you very much for your detailed explanations! UPD. Updated version 1.47.0 is working! |
1. What were you trying to do?
Running vg giraffe using the following command:
I was running it on a LSF cluster. The worker node had 240 GB of RAM and 64 cores.
2. What did you want to happen?
For the command to complete successfully.
3. What actually happened?
The command crashed with the following error message:
4. If you got a line like
Stack trace path: /somewhere/on/your/computer/stacktrace.txt
, please copy-paste the contents of that file here:Here is the main problem: because I run on LSF worker node, and /tmp is not synchronised over NSF, I am unable to access to the stacktrace file. I tried overriding the path by setting $TMPDIR, but the command ignores that and still writes to /tmp.
I think the problem is happening in this part of the code:
vg/src/crash.cpp
Line 145 in 531b4d9
5. What data and command can the vg dev team use to make the problem happen?
N/A. The input files weigh about 30 GB, I cannot share them publicly, but can send to the development team directly if needed.
6. What does running
vg version
say?The text was updated successfully, but these errors were encountered: