-
Notifications
You must be signed in to change notification settings - Fork 42
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' issue #88
Comments
Hello! I had the same problem,and I browsed all the issues without finding any methods to slove it. |
I run into the same problem. |
Hey, I am having the same issue right now. I even tried to install an older version of clipper but that too gave me the same error, wondering if anyone has come up with a solution.
|
Hi, Does any one have solved the bug Segmentation fault (core dumped) shown when run clipper? Pinpin |
Hi, got the same issue. New install on Ubuntu 22.04 and using the environment causes clipper to segmentation fault - does anybody have a solution for that? Or some idea what to change, we have so far tried to change the gcc version to 8.x, tried several packages higher and lower of the proposed versions yet still we get to a point where clipper just faults without much additional information. Any help would be amazing. |
Same issue. Repo seems dead. |
same issue |
Hi! Sorry for the delay. It can be related to the C extensions. Please make use of this docker image: https://hub.docker.com/r/brianyee/clipper
…On Apr 25, 2023, 8:47 PM -0700, Chirag Parsania, Ph.D. ***@***.***>, wrote:
same issue
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Hi, docker://brianyee/clipper:6594e71 |
I initially thought I cannot use the docker, because I need a newer reference genome (mm39). However, this is not needed during installation and can be added later. I briefly describe what I did in case someone needs something similar: |
Hello!
I re-installed clipper but error message came out.
I used 'conda env create -f environment3.yml'. I tried to fix it but it didn't work.
Is there anyone same problem like me?
Thanks!
Dahun
The text was updated successfully, but these errors were encountered: