-
Notifications
You must be signed in to change notification settings - Fork 46
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 at startup, release 3.2.1 #115
Comments
no ideas so far, linux 64-bit linux is a main target, this kind of crash is quite weird. Try running with debug logs, maybe there is any clue. Do you have many peers connected? |
Not sure how to see how many peers I have connected - I don't think I've ever changed any peer-related options. In any case, I think it crashes while starting up - it shouldn't have connected to many peers at that time, correct? I tried deleting my ~/.mldonkey dir and running it cleanly with
In case the OCaml compiler version made a difference, I tried building with 4.10.2 and 4.08.0 (earlier ones wouldn't install for me, I guess because the rest of the system is too new), with the same results... |
please show what the following patch outputs
|
Here you go:
|
that is a very generous file limit 🤔 |
I used to run it via a systemd user unit, but until it works again, I'm running it from a normal login shell. There, "ulimit -n" returns 1024. But I noticed the following in the debug log:
|
do you mean it works without segfault in the normal login shell with 1024 ulimit? can you still show ulimit for systemd unit? |
Sorry I wasn't clear, I meant that since I couldn't get it to run from the login shell, I hadn't tried starting it via systemd. I just tried it and the results are the same (also ulimit -n is still 1024 when started from systemd). But I hadn't tested upping the ulimit -n value. I tried with So, was the 1024 limit too low or the cause is something else which was causing it to get an incorrect value? If I'm following the code right, I think it's the result of getdtablesize(), whose man page states:
Maybe that's what was happening? |
yes, apparently something with limits, but idu exactly what
|
Hello! I've been running mldonkey for some years in a Debian unstable vm. Recently, after some upgrade, it ceased starting up with a message about incompatible libraries and I discovered the package had been dropped from Debian, so I thought I could compile it locally from source. I built it via opam as follows:
Unfortunately it always segfaults shortly after startup, regardless of type of build chosen. Here's the backtrace:
I'm attaching the configure and build logs:
configure.txt
build.txt
I'd appreciate any ideas or directions. Thanks!
The text was updated successfully, but these errors were encountered: