Bitcoin Forum
July 23, 2018, 12:34:52 PM *
News: Latest stable version of Bitcoin Core: 0.16.1  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 [326] 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 ... 847 »
  Print  
Author Topic: OFFICIAL CGMINER mining software thread for linux/win/osx/mips/arm/r-pi 4.10.0  (Read 5757020 times)
This is a self-moderated topic. If you do not want to be moderated by the person who started this topic, create a new topic.
Luke-Jr
Legendary
*
Offline Offline

Activity: 2394
Merit: 1001



View Profile
August 09, 2012, 04:15:44 PM
 #6501

The crash in libcurl was tracked down with the help of Kano. Interestingly this bug was always there but because previous versions queued so much extra, the number of "curls" in existence never dropped low enough to hit the bug.
Of course, despite being credited to Kano, this was debugged by me, and actually originally fixed in BFGMiner 2.6.3:
Code:
commit 1946c806922a66935856c32b6ca12d10db033b07
Author: Luke Dashjr <luke-jr+git@utopios.org>
Date:   Sun Aug 5 22:50:24 2012 +0000

    Bugfix: Check list_empty in pop_curl_entry after condition wait
    
    pthread_cond_signal wakes AT LEAST one thread, so it's possible the freed up curl has already been taken
lulz - it was the one you copied:
https://github.com/ckolivas/cgminer/commit/c7bcad653b79ee54429aec4964f4aa80e49db1d1
to here:
https://github.com/luke-jr/bfgminer/commit/c7bcad653b79ee54429aec4964f4aa80e49db1d1
(see the same commit numbers ...)
Is this the first time you expressed your absolute ignorance of how git works in public?
...
Hmm, when was the last one ... oh yeah I remember ... about 2 weeks ago ...
"I'm not a git export" ... Cheesy
https://bitcointalk.org/index.php?topic=28402.msg1055547#msg1055547
That was sarcasm, since you very well knew you were stealing credit for this fix. Or are you going to claim it's just coincidence that you found it and fixed it a few days after BFGMiner, and did so in practically the same way? Just like you "found and fixed" the JSON string encode error that you just submitted a fix to CGMiner for under your own name only hours after I wrote a nearly identical fix for BFGMiner and mentioned it on the forum?

1532349292
Hero Member
*
Offline Offline

Posts: 1532349292

View Profile Personal Message (Offline)

Ignore
1532349292
Reply with quote  #2

1532349292
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
P_Shep
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000


View Profile
August 09, 2012, 06:00:26 PM
 #6502

Get over it Luke.

Simple problems are going be solved in the same simple way. There's nothing novel or unique about the code you write. It's all straight forward and intuitive.

Neither of these two examples have the same, copied solution. They were both solved independently in similar ways as they are both soving the same problem. It's no suprise the timing is also similar as these issue are being found at the same time.

You are not a coding god. Anyone can come up with the same ideas as you.
Luke-Jr
Legendary
*
Offline Offline

Activity: 2394
Merit: 1001



View Profile
August 09, 2012, 06:38:59 PM
 #6503

Neither of these two examples have the same, copied solution. They were both solved independently in similar ways as they are both soving the same problem. It's no suprise the timing is also similar as these issue are being found at the same time.
I don't know why you're defending his obvious theft. They do have the same copied solution, even if Kano made a poor effort to obfuscate it; while the first one might have only had one or two ways it could be fixed, this last one has numerous possible solutions (the most obvious being significantly better than the one I ended up taking except for making merging from cgminer harder if cgminer hadn't adopted it too); yet in both cases Kano used the exact same solution - only trivial/non-substantial changes to the syntax/names were made.

Neither of these bugs were in fact found in cgminer: the curlring issue was one I experienced myself personally, spent hours debugging, and finally identified a solution for; the only way Kano would have even known it existed was by reading BFGMiner's commit log; the JSON escaping issue only really affect BFGMiner because its compiled-in prefix on Windows uses backslashes.

P_Shep
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000


View Profile
August 09, 2012, 06:45:54 PM
 #6504

Neither of these bugs were in fact found in cgminer: the curlring issue was one I experienced myself personally, spent hours debugging, and finally identified a solution for; the only way Kano would have even known it existed was by reading BFGMiner's commit log; the JSON escaping issue only really affect BFGMiner because its compiled-in prefix on Windows uses backslashes.

Maybe Kano is just better than you then?

There were a number of bug reports posted here in this thread pointing to libcurl being the source of locking up. Shortly after that, the fix was made. It's not a giant leap to assume that, in fact, they solved the problem.
streetuff
Full Member
***
Offline Offline

Activity: 150
Merit: 100



View Profile
August 09, 2012, 06:46:36 PM
 #6505

Neither of these two examples have the same, copied solution. They were both solved independently in similar ways as they are both soving the same problem. It's no suprise the timing is also similar as these issue are being found at the same time.
I don't know why you're defending his obvious theft. They do have the same copied solution, even if Kano made a poor effort to obfuscate it; while the first one might have only had one or two ways it could be fixed, this last one has numerous possible solutions (the most obvious being significantly better than the one I ended up taking except for making merging from cgminer harder if cgminer hadn't adopted it too); yet in both cases Kano used the exact same solution - only trivial/non-substantial changes to the syntax/names were made.

Neither of these bugs were in fact found in cgminer: the curlring issue was one I experienced myself personally, spent hours debugging, and finally identified a solution for; the only way Kano would have even known it existed was by reading BFGMiner's commit log; the JSON escaping issue only really affect BFGMiner because its compiled-in prefix on Windows uses backslashes.

you have been told to get the fuck out of this thread several times. i'm no mod here but i have something to complain about... most of BigFuckingCunt miner is based on conmans work...
muqali
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile
August 09, 2012, 07:10:52 PM
 #6506

Aren't most of what people are arguing about code-wise GPL or similar open licenses? If so, copying is a non-issue and is to be applauded. It benefits the greater good.

donations BTC: 1CaCwo4xneTqTLEdomW76Cg5NteZyvXi1c
donations LTC: LTcasvjtLuN92ks1Pc1qtkvE9PswsXEbev
Luke-Jr
Legendary
*
Offline Offline

Activity: 2394
Merit: 1001



View Profile
August 09, 2012, 07:17:37 PM
 #6507

Neither of these two examples have the same, copied solution. They were both solved independently in similar ways as they are both soving the same problem. It's no suprise the timing is also similar as these issue are being found at the same time.
I don't know why you're defending his obvious theft. They do have the same copied solution, even if Kano made a poor effort to obfuscate it; while the first one might have only had one or two ways it could be fixed, this last one has numerous possible solutions (the most obvious being significantly better than the one I ended up taking except for making merging from cgminer harder if cgminer hadn't adopted it too); yet in both cases Kano used the exact same solution - only trivial/non-substantial changes to the syntax/names were made.

Neither of these bugs were in fact found in cgminer: the curlring issue was one I experienced myself personally, spent hours debugging, and finally identified a solution for; the only way Kano would have even known it existed was by reading BFGMiner's commit log; the JSON escaping issue only really affect BFGMiner because its compiled-in prefix on Windows uses backslashes.

you have been told to get the fuck out of this thread several times. i'm no mod here but i have something to complain about... most of BigFuckingCunt miner is based on conmans work...
Go troll elsewhere. CGMiner was based on Garzik's work in the same way: Con added GPU support, and I added FPGA support. Until ASICs were announced, Con had nothing to do with FPGA support.

Aren't most of what people are arguing about code-wise GPL or similar open licenses? If so, copying is a non-issue and is to be applauded. It benefits the greater good.
Copying is not the issue. The issue is Con and Kano passing off others' work as their own.

P_Shep
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000


View Profile
August 09, 2012, 07:25:37 PM
 #6508

A bit like taking some header files and removing the author/copywrite info?
Luke-Jr
Legendary
*
Offline Offline

Activity: 2394
Merit: 1001



View Profile
August 09, 2012, 07:31:39 PM
 #6509

A bit like taking some header files and removing the author/copywrite info?
Please don't make implied accusations that aren't true, kthx.

muqali
Full Member
***
Offline Offline

Activity: 182
Merit: 100


View Profile
August 09, 2012, 07:45:00 PM
 #6510

Neither of these two examples have the same, copied solution. They were both solved independently in similar ways as they are both soving the same problem. It's no suprise the timing is also similar as these issue are being found at the same time.
I don't know why you're defending his obvious theft. They do have the same copied solution, even if Kano made a poor effort to obfuscate it; while the first one might have only had one or two ways it could be fixed, this last one has numerous possible solutions (the most obvious being significantly better than the one I ended up taking except for making merging from cgminer harder if cgminer hadn't adopted it too); yet in both cases Kano used the exact same solution - only trivial/non-substantial changes to the syntax/names were made.

Neither of these bugs were in fact found in cgminer: the curlring issue was one I experienced myself personally, spent hours debugging, and finally identified a solution for; the only way Kano would have even known it existed was by reading BFGMiner's commit log; the JSON escaping issue only really affect BFGMiner because its compiled-in prefix on Windows uses backslashes.

you have been told to get the fuck out of this thread several times. i'm no mod here but i have something to complain about... most of BigFuckingCunt miner is based on conmans work...
Go troll elsewhere. CGMiner was based on Garzik's work in the same way: Con added GPU support, and I added FPGA support. Until ASICs were announced, Con had nothing to do with FPGA support.

Aren't most of what people are arguing about code-wise GPL or similar open licenses? If so, copying is a non-issue and is to be applauded. It benefits the greater good.
Copying is not the issue. The issue is Con and Kano passing off others' work as their own.

Ah, an accrediting issue. As I know nothing about who did what I'll bow out.

donations BTC: 1CaCwo4xneTqTLEdomW76Cg5NteZyvXi1c
donations LTC: LTcasvjtLuN92ks1Pc1qtkvE9PswsXEbev
mc_lovin
Legendary
*
Offline Offline

Activity: 1162
Merit: 1000


www.bitcointrading.com


View Profile WWW
August 09, 2012, 09:07:06 PM
 #6511

Neither of these two examples have the same, copied solution. They were both solved independently in similar ways as they are both soving the same problem. It's no suprise the timing is also similar as these issue are being found at the same time.
I don't know why you're defending his obvious theft. They do have the same copied solution, even if Kano made a poor effort to obfuscate it; while the first one might have only had one or two ways it could be fixed, this last one has numerous possible solutions (the most obvious being significantly better than the one I ended up taking except for making merging from cgminer harder if cgminer hadn't adopted it too); yet in both cases Kano used the exact same solution - only trivial/non-substantial changes to the syntax/names were made.

Neither of these bugs were in fact found in cgminer: the curlring issue was one I experienced myself personally, spent hours debugging, and finally identified a solution for; the only way Kano would have even known it existed was by reading BFGMiner's commit log; the JSON escaping issue only really affect BFGMiner because its compiled-in prefix on Windows uses backslashes.

you have been told to get the fuck out of this thread several times. i'm no mod here but i have something to complain about... most of BigFuckingCunt miner is based on conmans work...
Go troll elsewhere. CGMiner was based on Garzik's work in the same way: Con added GPU support, and I added FPGA support. Until ASICs were announced, Con had nothing to do with FPGA support.

Aren't most of what people are arguing about code-wise GPL or similar open licenses? If so, copying is a non-issue and is to be applauded. It benefits the greater good.
Copying is not the issue. The issue is Con and Kano passing off others' work as their own.

P_Shep
Legendary
*
Offline Offline

Activity: 1176
Merit: 1000


View Profile
August 09, 2012, 09:07:37 PM
 #6512

Copying is not the issue. The issue is Con and Kano passing off others' work as their own.

At the end of the day it's just your paranoid (delusional?) opinon that they took your code, changed it then submitted it themselves.

Since all this code is GPL, would the easier solution for them not simply be submit your commit, which would involve almost zero effort, rather then re-arrange your code? What is to gain? What's their motive?
streetuff
Full Member
***
Offline Offline

Activity: 150
Merit: 100



View Profile
August 09, 2012, 09:14:01 PM
 #6513

ignoring the ginger now. because gingers are scary!
mc_lovin
Legendary
*
Offline Offline

Activity: 1162
Merit: 1000


www.bitcointrading.com


View Profile WWW
August 09, 2012, 09:14:19 PM
 #6514

Copying is not the issue. The issue is Con and Kano passing off others' work as their own.

At the end of the day it's just your paranoid (delusional?) opinon that they took your code, changed it then submitted it themselves.

Since all this code is GPL, would the easier solution for them not simply be submit your commit, which would involve almost zero effort, rather then re-arrange your code? What is to gain? What's their motive?
Isn't BFG a fork of cgminer?  So he came in, added a few lines, and then now HE'S complaining about stolen code?

Luke-Jr
Legendary
*
Offline Offline

Activity: 2394
Merit: 1001



View Profile
August 09, 2012, 09:24:23 PM
 #6515

Copying is not the issue. The issue is Con and Kano passing off others' work as their own.

At the end of the day it's just your paranoid (delusional?) opinon that they took your code, changed it then submitted it themselves.

Since all this code is GPL, would the easier solution for them not simply be submit your commit, which would involve almost zero effort, rather then re-arrange your code? What is to gain? What's their motive?
Isn't BFG a fork of cgminer?  So he came in, added a few lines, and then now HE'S complaining about stolen code?
It was a fork of the original CGMiner. I rewrote a lot of code to make it possible to have other drivers (the original was CPU and GPU as mostly separate code), and added support for FPGAs. Con took that code back into CGMiner, and eventually forked his copy of it.

So in short, cpu-miner was forked to CGMiner for GPU support. CGMiner was forked to BFGMiner for FPGA support. BFGMiner was then forked back into CGMiner for political reasons.

Also, I make sure to attribute even Con and Kano's (indirect) contributions to BFGMiner.

Luke-Jr
Legendary
*
Offline Offline

Activity: 2394
Merit: 1001



View Profile
August 09, 2012, 09:26:45 PM
 #6516

Since all this code is GPL, would the easier solution for them not simply be submit your commit, which would involve almost zero effort, rather then re-arrange your code? What is to gain? What's their motive?
Detraction and trolling me is their apparent motive.

Maybe also related to this:
Quote
<conman> I don't even take his code pushes even if they're apparently bugfixes

-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1113


Ruu \o/


View Profile WWW
August 09, 2012, 09:34:54 PM
 #6517

People seem to not understand it is entirely possible 2 people arrive at the same solution to the same bug at different times. This complaint is now about something like a one line bugfix with exactly those circumstances. Paranoid delusions indeed.

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
mc_lovin
Legendary
*
Offline Offline

Activity: 1162
Merit: 1000


www.bitcointrading.com


View Profile WWW
August 09, 2012, 10:18:06 PM
 #6518

Is there a place to get older version of cgminer?  I need 2.5.0, I think 2.6.x is the problem I'm facing right now...

Luke-Jr
Legendary
*
Offline Offline

Activity: 2394
Merit: 1001



View Profile
August 09, 2012, 10:20:35 PM
 #6519

Is there a place to get older version of cgminer?  I need 2.5.0, I think 2.6.x is the problem I'm facing right now...
http://ck.kolivas.org/apps/cgminer/cgminer-2.5/

-ck
Moderator
Legendary
*
Offline Offline

Activity: 2590
Merit: 1113


Ruu \o/


View Profile WWW
August 09, 2012, 10:24:10 PM
 #6520

Is there a place to get older version of cgminer?  I need 2.5.0, I think 2.6.x is the problem I'm facing right now...
All older versions here:
http://ck.kolivas.org/apps/cgminer/

Primary developer/maintainer for cgminer and ckpool/ckproxy.
ZERO FEE Pooled mining at ckpool.org 1% Fee Solo mining at solo.ckpool.org
-ck
Pages: « 1 ... 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 [326] 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 ... 847 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!