Skip to content
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 on 2.3.1 OS X #27

Closed
deutrino opened this issue Jun 21, 2013 · 16 comments
Closed

Segmentation fault on 2.3.1 OS X #27

deutrino opened this issue Jun 21, 2013 · 16 comments

Comments

@deutrino
Copy link

2.3.1 ran for about 2 hours on OS X 10.7, then segfaulted overnight. Now it segfaults 100% of the time right after startup:

$ nice -n 18 ./minerd -c mycfg.json 
[2013-06-21 08:50:49] 4 miner threads started, using 'scrypt' algorithm.
[2013-06-21 08:50:49] Starting Stratum on stratum+tcp://redacted
Segmentation fault: 11

Edit: This was using the downloaded binary. I will be able to report performance on other flavors of OS X in a little while.

@pooler
Copy link
Owner

pooler commented Jun 21, 2013

Could you please mail me (pooler at litecoinpool dot org) your exact configuration file and the output of minerd when you add "-D -P" to the command line options?

@deutrino
Copy link
Author

Okay. Note, I've just built the miner from source and so far (like 30 sec) it hasn't segfaulted. I will mail you shortly.

@deutrino
Copy link
Author

Running my locally compiled version seems to have 'cleared' the issue, I'll go back to the downloaded binary, tee the output and wait for it to segfault again and mail you that.

@deutrino
Copy link
Author

Another segfault on 10.7.5 on a different machine overnight using the downloaded binary. Restarted with -D -P and it took a little while but segfaulted again. Emailing you the dump.

Edit: 'screen' ate most of the dump. :/ Going to re-run in a terminal.

@deutrino
Copy link
Author

Two more segfaults overnight on 10.6.8. Can't get them to segfault again right out of the gate like with the first machine, so I'm running them all with -D -P and waiting, will send dumps when I get any.

@deutrino
Copy link
Author

Caught 3 on 10.6.8 and 10.7.5, Core 2 Duo and i5 CPUs. So far no problem on Linux. Emailing you hopefully-useful dumps.

@deutrino
Copy link
Author

So far on at least one machine, a locally-compiled version of 2.3.1 has run for a number of hours with no segfault. This is on the 10.7 machine. The binary is also 147180 bytes compared to the downloadable's 466492.

@pooler
Copy link
Owner

pooler commented Jun 22, 2013

In case you are wondering, the size of the downloadable binary is due to it being statically linked to libcurl.

@deutrino
Copy link
Author

I figured static linking. I'm building it with an older xcode and homebrew - happy to do whatever I can to help debug. Just let me know.

Sent from my device

On Sat, 22 Jun 2013 10:16:56 -0700, pooler notifications@github.com wrote:

In case you are wondering, the size of the downloadable binary is due to it being statically linked to libcurl.


Reply to this email directly or view it on GitHub:
#27 (comment)

@deutrino
Copy link
Author

A lot of my emails to you bounced after a couple days (litecoinpool.com???) - do you have what you need from me?

@pooler
Copy link
Owner

pooler commented Jun 24, 2013

I only received two emails from you, one on June 21 at 18:12 UTC and one on June 22 at 20:28 UTC. Mind that the host part of my email address is litecoinpool.org, not litecoinpool.com as you wrote in your message above.
Anyway, I have just pushed a commit fixing a bug that can cause a segmentation fault on certain Stratum data, could you please try it out?

@deutrino
Copy link
Author

Would you like me to download the precompiled OS X binary? My local builds of 2.3.1 were all running fine.

@pooler
Copy link
Owner

pooler commented Jun 25, 2013

Yes, please re-download the OS X binary here.

@deutrino
Copy link
Author

Done. Running, waiting for segfaults.

@deutrino
Copy link
Author

So far so good on the 10.7 box. Prior version would likely have segfaulted by now. Have not yet installed on the 10.6 boxes.

@deutrino
Copy link
Author

I think you nailed it. All of them are running fine now. Thanks for the amazing turnaround time on this bug! Really appreciated!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants