[LOCKED] cpuminer-opt v3.12.3, open source optimized multi-algo CPU miner

[joblo]

i really do apologize for being a pain in the ass. I compiled on Ubuntu 16.04. i hope this is the output your asking for. If not how do i find the other
name@name-VPCEH32FX:~/cpuminer-opt$ ./cpuminer -a hmq1725 -o stratum+tcp://boat.suprnova.cc:4156 -u twiztid1.2 -p x -t 2

      **********  cpuminer-opt 3.5.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU:        Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
CPU features: SSE2 AES AVX
SW built on Feb 19 2017 with GCC 5.4.0
SW features: SSE2 AES AVX
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2 AES AVX

[2017-02-19 13:30:09] Starting Stratum on stratum+tcp://boat.suprnova.cc:4156
[2017-02-19 13:30:09] Binding thread 0 to cpu 0 (mask 1)
[2017-02-19 13:30:09] 2 miner threads started, using 'hmq1725' algorithm.
[2017-02-19 13:30:09] Binding thread 1 to cpu 1 (mask 2)
[2017-02-19 13:30:09] Stratum session id: deadbeefcafebabe382b000000000000
[2017-02-19 13:30:12] stratum extranonce subscribe timed out
[2017-02-19 13:30:12] DEBUG: job_id='8e47' extranonce2=00000000 ntime=58a9f235
[2017-02-19 13:30:12] Stratum difficulty set to 1 (0.00002)
[2017-02-19 13:30:12] hmq1725 block 29228, diff 3.345
[2017-02-19 13:30:13] DEBUG: hash <= target
Hash:   00004bd64e027695caea3732e8c8c775d6c12260d3829714b213d30aa27f960d
Target: 0000ffff00000000000000000000000000000000000000000000000000000000
*** stack smashing detected ***: ./cpuminer terminated
Aborted (core dumped)
name@name-VPCEH32FX:~/cpuminer-opt$

Thanks. This tells me where it crashed, after finding a nonce but before displaying the hash message.
It's going to be a difficult troubleshooting and I need every clue I can get.

Can you tell me about Windows? Did you compile it or use the binaries? What kind of CPU?

On Linux can you try compiling with -march=core2  instead of -march=native. This will cause some different
code to run and I want to know if it crashes as well.

[1714979270]

1714979270

[1714979270]

1714979270

[1714979270]

1714979270

[YourMom420]

on windows i used the precompiled from cryptominingblog. exact same cpu. give me a few minutes and ill recompile. same thing. i may just give up on this algo lol. might not be worth the trouble with my shitty comp.
         **********  cpuminer-opt 3.5.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU:        Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
CPU features: SSE2 AES AVX
SW built on Feb 19 2017 with GCC 5.4.0
SW features: SSE2
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2

[2017-02-19 14:15:37] Starting Stratum on stratum+tcp://boat.suprnova.cc:4156
[2017-02-19 14:15:37] Binding thread 0 to cpu 0 (mask 1)
[2017-02-19 14:15:37] 2 miner threads started, using 'hmq1725' algorithm.
[2017-02-19 14:15:37] Binding thread 1 to cpu 1 (mask 2)
[2017-02-19 14:15:38] Stratum session id: deadbeefcafebabe4a2b000000000000
[2017-02-19 14:15:41] stratum extranonce subscribe timed out
[2017-02-19 14:15:41] DEBUG: job_id='8e98' extranonce2=00000000 ntime=58a9fcd9
[2017-02-19 14:15:41] Stratum difficulty set to 1 (0.00002)
[2017-02-19 14:15:41] hmq1725 block 29284, diff 2.743
[2017-02-19 14:15:49] DEBUG: hash <= target
Hash:   00003f4440d4cd15afcad7a6d0e24960d04db69040e9e7447dfbf7307610aed3
Target: 0000ffff00000000000000000000000000000000000000000000000000000000
*** stack smashing detected ***: ./cpuminer terminated
Aborted (core dumped)
name@name-VPCEH32FX:~/cpuminer-opt$

[joblo]

on windows i used the precompiled from cryptominingblog. exact same cpu. give me a few minutes and ill recompile. same thing. i may just give up on this algo lol. might not be worth the trouble with my shitty comp.

Cryptominingblog stopped building binaries of cpuminer-opt a long time ago. Sigh.

[YourMom420]

on windows i used the precompiled from cryptominingblog. exact same cpu. give me a few minutes and ill recompile. same thing. i may just give up on this algo lol. might not be worth the trouble with my shitty comp.

Cryptominingblog stopped building binaries of cpuminer-opt a long time ago. Sigh.

thats the one that works for me :/...only on windows though.

[integrale]

         **********  cpuminer-opt 3.5.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU:         Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
CPU features: SSE2 AES AVX
SW built on Feb 16 2017 with GCC 5.4.0
SW features: SSE2 AES AVX
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2 AES AVX

[2017-02-21 00:56:57] Starting Stratum on stratum+tcp://yiimp.ccminer.org:3747
[2017-02-21 00:56:57] 8 miner threads started, using 'hmq1725' algorithm.
[2017-02-21 00:56:57] Stratum difficulty set to 8 (0.00012)
[2017-02-21 00:56:57] hmq1725 block 31296, diff 4.637
[2017-02-21 00:56:59] hmq1725 block 31297, diff 4.637
*** stack smashing detected ***: ./cpuminer terminated
*** stack smashing detected ***: ./cpuminer terminated
Abgebrochen (Speicherabzug geschrieben)
sklave@miner-HP-Compaq-8200:~/joblo8$

im so happy im not the only one 

[joblo]

        **********  cpuminer-opt 3.5.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU:         Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
CPU features: SSE2 AES AVX
SW built on Feb 16 2017 with GCC 5.4.0
SW features: SSE2 AES AVX
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2 AES AVX

[2017-02-21 00:56:57] Starting Stratum on stratum+tcp://yiimp.ccminer.org:3747
[2017-02-21 00:56:57] 8 miner threads started, using 'hmq1725' algorithm.
[2017-02-21 00:56:57] Stratum difficulty set to 8 (0.00012)
[2017-02-21 00:56:57] hmq1725 block 31296, diff 4.637
[2017-02-21 00:56:59] hmq1725 block 31297, diff 4.637
*** stack smashing detected ***: ./cpuminer terminated
*** stack smashing detected ***: ./cpuminer terminated
Abgebrochen (Speicherabzug geschrieben)
sklave@miner-HP-Compaq-8200:~/joblo8$

im so happy im not the only one  

Both are with GCC 5.4.0, I compile with 4.8.4. It's the best clue so far.

There were some problem reported a long time ago with newer compilers. I'll have to try to find
that discussion unless someone else finds it first. I thought it had been resolved but don't recall how.

Found this.

http://stackoverflow.com/questions/39237085/stack-smashing-detected-comes-in-ubuntu-16-04

It's worth a try. If nothing else it will blow up somewhere else giving another clue.

Edit: as far as root cause goes, I've reviewed the code many times for rogue pointers that could corrupt
the stack (Im very familiar with my issues with pointer arithmetic) but can't find anything suspicious.

It may be a stack overflow which can go unoticed if it it doesn't go too far. That could explain why it
works when compiled with GCC 4.8.4 presumably with no stack protector.

If it is a stack overflow the next release will have reduced stack usage. The context struct for this algo
is the biggest of any algos, including xevan so I've moved it from local to global In a sense it is the canary.
I may move more context structs if this proves to be the issue.

[integrale]

so far so good . thank you for the response
but how to downgrade or fix by myself ,   and is it worth because you said you will try to fix this in next releases

[joblo]

so far so good . thank you for the response
but how to downgrade or fix by myself ,   and is it worth because you said you will try to fix this in next releases

If it works with stack protector disabled go with it until the next release, then try reenabling it to see
if the problem is fixed.

[Epsylon3]

Code:

valgrind --leak-check=full -v --log-file=report.log ./cpuminer ....

that will use secure memory allocations and logs overflows etc. This error is happening if you write too far in an array... and indeed doesnt crash all the time..

[joblo]

I'm not sure what I'm looking for with valgrind. leak-check is done at program exit and reports
some potential leaks that appear to be false positives. Regardless leaks are not the issue,

Memcheck seems to be what I'm looking for and it appears to be enabled by default. But I didn't
see anything that stood out. There was no mention of Memcheck other than in the report header
and no mention of any stack problems other than the suspected leaks. As these appear to be in
systen code allocating a stack and the man page does warn of false positives i don't
think they are significant. Here's a sample showing one of 4 identical reports and the summary.

I saw no difference after implementing the smaller stack frame.

Code:

==20686== 320 bytes in 1 blocks are possibly lost in loss record 72 of 80
==20686==    at 0x4C2CC70: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==20686==    by 0x4012E54: allocate_dtv (dl-tls.c:296)
==20686==    by 0x4012E54: _dl_allocate_tls (dl-tls.c:460)
==20686==    by 0x50A1DA0: allocate_stack (allocatestack.c:589)
==20686==    by 0x50A1DA0: pthread_create@@GLIBC_2.2.5 (pthread_create.c:500)
==20686==    by 0x4059FF: main (in /home/coin/devel/cpuminer/cpuminer/3.5.9/cpuminer-opt-3.5.9-dev/cpuminer)
==20686==
==20686== LEAK SUMMARY:
==20686==    definitely lost: 0 bytes in 0 blocks
==20686==    indirectly lost: 0 bytes in 0 blocks
==20686==      possibly lost: 1,280 bytes in 4 blocks
==20686==    still reachable: 133,323 bytes in 84 blocks
==20686==         suppressed: 0 bytes in 0 blocks
==20686== Reachable blocks (those to which a pointer was found) are not shown.
==20686== To see them, rerun with: --leak-check=full --show-leak-kinds=all
==20686==
==20686== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
==20686== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)

[joblo]

I was looking at sia in cpuminer-multi, it didn't submit a share after several minutes although it
appeared to be hashing sanely. Dos it work? It looks like the wrong nonce offset [19] is used
all through scanhash_sia but [8] (32 bytes) is used in miner_thread.

[integrale]

until now nothing has solved the problem ,
i found this  here:  from this source
http://stackoverflow.com/questions/2340259/how-to-turn-off-gcc-compiler-optimization-to-enable-buffer-overflow

maybe something from works

On newer distros (as of 2016), it seems that PIE is enabled by default so you will need to disable it explicitly when compiling.

Here's a little summary of commands which can be helpful when playing locally with buffer overflow exercises in general:

Disable canary:

gcc vuln.c -o vuln_disable_canary -fno-stack-protector ./build.sh       << tested     no succes   same error (stack overflow   terminated) 

Disable DEP:

gcc vuln.c -o vuln_disable_dep -z execstack

Disable PIE:

gcc vuln.c -o vuln_disable_pie -no-pie

Disable all of protection mechanisms listed above (warning: for local testing only):

gcc vuln.c -o vuln_disable_all -fno-stack-protector -z execstack -no-pie



have also tried like Epsylon adviced , no succes   

[joblo]

until now nothing has solved the problem ,
i found this  here:  from this source
http://stackoverflow.com/questions/2340259/how-to-turn-off-gcc-compiler-optimization-to-enable-buffer-overflow

maybe something from works

On newer distros (as of 2016), it seems that PIE is enabled by default so you will need to disable it explicitly when compiling.

Here's a little summary of commands which can be helpful when playing locally with buffer overflow exercises in general:

Disable canary:

gcc vuln.c -o vuln_disable_canary -fno-stack-protector ./build.sh       << tested     no succes   same error (stack overflow   terminated) 

Disable DEP:

gcc vuln.c -o vuln_disable_dep -z execstack

Disable PIE:

gcc vuln.c -o vuln_disable_pie -no-pie

Disable all of protection mechanisms listed above (warning: for local testing only):

gcc vuln.c -o vuln_disable_all -fno-stack-protector -z execstack -no-pie



have also tried like Epsylon adviced , no succes   

-fno-stack-protector should prevent the stack smashing detection but may still result in a segfault. That would
be a successful test as it indicates the stack smashing detection is not causing a problem, only detecting
a problem.

I presume you saw nothing unusual when running with valgrind. I would expect some extra data surrouding
the crash.

[integrale]

i have the logfile   "report.log"    from Eypsylon version of CL    but its a huge file .
if it helps  how can i deliver it to you     or simply posting here ?

[joblo]

i have the logfile   "report.log"    from Eypsylon version of CL    but its a huge file .
if it helps  how can i deliver it to you     or simply posting here ?

Just look for keywords like Memcheck. stack, error, etc, as well as the last few lines when it crashed.
I don't know exactly what to look for, just anything suspicious that indicates problems with the stack.

Did you try compiling with -fno-stack-protector?

[integrale]

not yet tried , but i will do so


here the last lines from report.log

==28886== LEAK SUMMARY:
==28886==    definitely lost: 0 bytes in 0 blocks
==28886==    indirectly lost: 0 bytes in 0 blocks
==28886==      possibly lost: 2,240 bytes in 7 blocks
==28886==    still reachable: 305,618 bytes in 785 blocks
==28886==         suppressed: 0 bytes in 0 blocks
==28886==
==28886== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
==28886== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)

[integrale]

sklave@miner-HP-Compaq-8200:~/joblo8$ valgrind --leak-check=full -v --log-file=report.log ./cpuminer -a hmq1725 -t 4 -o stratum+tcp://yiimp.ccminer.org:3747 -u B6DE2BVjsbWp6u4EukeHKTU2auhBn5YUNU -p x,c=BOAT,stats

         **********  cpuminer-opt 3.5.8  ***********
     A CPU miner with multi algo support and optimized for CPUs
     with AES_NI and AVX extensions.
     BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
     Forked from TPruvot's cpuminer-multi with credits
     to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
     Wolf0, Jeff Garzik and Optiminer.

CPU:         Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz <<----------- isnt it strange   missdetecting my CPU  built in is i7 2600
CPU features: SSE2 AES AVX
SW built on Feb 16 2017 with GCC 5.4.0
SW features: SSE2 AES AVX
Algo features: SSE2 AES AVX AVX2
Start mining with SSE2 AES AVX

[2017-02-21 20:21:57] 4 miner threads started, using 'hmq1725' algorithm.
[2017-02-21 20:21:58] Starting Stratum on stratum+tcp://yiimp.ccminer.org:3747
[2017-02-21 20:21:58] Stratum difficulty set to 8 (0.00012)
[2017-02-21 20:21:58] hmq1725 block 32712, diff 1.793
*** stack smashing detected ***: ./cpuminer terminated
*** stack smashing detected ***: ./cpuminer terminated
killed
sklave@miner-HP-Compaq-8200:~/joblo8$


like this it takes about 30sec to crash

without :    valgrind --leak-check=full -v --log-file=report.log   it detects corect type of CPU

[joblo]

not yet tried , but i will do so


here the last lines from report.log

==28886== LEAK SUMMARY:
==28886==    definitely lost: 0 bytes in 0 blocks
==28886==    indirectly lost: 0 bytes in 0 blocks
==28886==      possibly lost: 2,240 bytes in 7 blocks
==28886==    still reachable: 305,618 bytes in 785 blocks
==28886==         suppressed: 0 bytes in 0 blocks
==28886==
==28886== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)
==28886== ERROR SUMMARY: 4 errors from 4 contexts (suppressed: 0 from 0)

No difference from mine. It looks like whatever is trippping the stack protection isn't
being seen by valgrind.

[joblo]

CPU:         Intel(R) Core(TM) i5-2300 CPU @ 2.80GHz <<----------- isnt it strange   missdetecting my CPU  built in is i7 2600

I get the same on my i7-6700K. Valgrind emulates a software CPU, no AVX2 yet.

[integrale]

i have no more idea , except switching GCC or to install 14.04         step back     grrrrr