-
Notifications
You must be signed in to change notification settings - Fork 2
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
Segmentation fault #1
Comments
Are you running this on a 32 bit machine? |
This was run in a 64 bits machine, with 1.5 TB of ram. |
I think this line provides a little insight to what's going on, The kernel is telling you that the process has an allocation of about 30 gigs. The segmentation fault is probably happening when you hit the upper limit and the kernel kills the process. I'm not sure how to fix this, but here are some resources that may help you out. Resident Set Size? Set the Limit setlimit |
Hi, |
Hi,
Thanks for having this nice library public!
I think I found a bug, or perhaps I stumbled into an undocumented limitation; I was building the suffix
array of a ~1.8GB sequence, as 32 bit integers and got a segmentation fault.
The steps to reproduce it are as follows:
from "typedef uint64_t uint_t;" to "typedef uint32_t uint_t;"
https://www.cs.helsinki.fi/u/dvalenzu/tmp/parallel_range_lite/genome_problematic.txt.7z
Then the following happens:
./main.o genome_problematic.txt
Segmentation fault (core dumped)
I don't think it is because of lack of memory, as I am runing this in a server with 1.5TB of ram.
and when I montitored the memory used I got the following:
/usr/bin/time --verbose ./main.o /home/scratch-ssd/dvalenzu/Data/genome_problematic.txt
(...)
Maximum resident set size (kbytes): 30819104
Best,
Daniel
The text was updated successfully, but these errors were encountered: