corrupted double-linked list? #28

1. 
   gavinandresen commented at 0:12 am on January 13, 2011: contributor

   tcatm reports:

   *** glibc detected *** ./bitcoind: corrupted double-linked list: 0x0a78b468 ***

   … possibly in listaccounts.

2. 
   tcatm commented at 0:18 am on January 13, 2011: none

   possibly in other RPC methods, too. It died with getaccountaddress in debug.log, but didn’t get glibc message as the terminal was closed.

   Version: 009d5fb41f3aa39baeeb3f72454cdc14459fc67e (Merge branch ’listaddresses’ into integration) with CORS patch (shouldn’t cause it, though)

   bitcoind: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15, not stripped

3. 
   tcatm commented at 11:14 pm on January 13, 2011: none

   I just noticed the following (line numbers might not match, I discovered this while re-ordering some code):

   In getaccountaddress() rpc.cpp:361: warning: control reaches end of non-void function

   edit: ArtForz and lfm on IRC said, that code should never return inside a CRITICAL_BLOCK()

4. 
   gavinandresen commented at 10:31 pm on January 15, 2011: contributor

   Returning from a CRITICAL_BLOCK is OK. CRITICAL_BLOCK uses local C++ objects to do the locking, which are guaranteed to be properly destructed no matter how the block is exited.
5. 
   gavinandresen commented at 1:53 pm on February 19, 2011: contributor

   More data: there have been a couple more reports of bitcoind crashing under heavy RPC load, although nobody has been able to reproduce.
6. 
   tril0byte commented at 5:12 pm on March 5, 2011: none

   how do we know this isn’t a hardware problem? does bitcoin check the consistency of its files and repair them automatically?
7. 
   jhyslop commented at 0:15 am on March 8, 2011: none

   gavinandresen, were those reports from different people, or from one person? If they were from different people I’d push hardware problems further down the list of suspects. I wouldn’t rule out hardware problems, of course.
8. 
   gavinandresen commented at 0:28 am on March 10, 2011: contributor

   jhyslop: bitcoind crashing/hanging reports were from other people (slush was one, I believe).

   I still haven’t seen it, running 3 or 4 instances of bitcoind on 2 or 3 different machines (Mac and Debian Linux).

9. 
   gavinandresen commented at 4:26 pm on August 9, 2011: contributor

   No further reports of this, I’m going to close.
10. gavinandresen closed this on Aug 9, 2011

    ---

11. kac- referenced this in commit a9b7d4ab80 on Jun 10, 2014
12. rdponticelli referenced this in commit e65183ae54 on Nov 26, 2014
13. dexX7 referenced this in commit b4ba45c619 on May 5, 2015
14. sdaftuar referenced this in commit c93d6cab64 on May 14, 2015
15. jtimon referenced this in commit be997831ca on Jun 23, 2015
16. ptschip referenced this in commit 128b60cc65 on Jun 9, 2016
17. MarcoFalke referenced this in commit 2ca7faab42 on Sep 30, 2016
18. n1bor referenced this in commit 2552cba38d on Oct 21, 2016
19. tempgit9 referenced this in commit 88d0275e77 on Jan 16, 2017
20. ptschip referenced this in commit 7a0bb44c93 on May 4, 2017
21. tmagik referenced this in commit 32daff9dda on Jul 1, 2017
22. Sjors referenced this in commit aa4e514038 on Aug 31, 2017
23. MarcoFalke referenced this in commit cedda1473d on Sep 29, 2017
24. laanwj referenced this in commit 22a6c1fd8f on Nov 30, 2017
25. laanwj referenced this in commit 9b80fc1498 on Nov 30, 2017
26. laanwj referenced this in commit dd49862a70 on Nov 30, 2017
27. classesjack referenced this in commit b52e409735 on Jan 2, 2018
28. HashUnlimited referenced this in commit 2340d25dbb on Mar 14, 2018
29. KrzysiekJ referenced this in commit 15c61a6d39 on Mar 28, 2018
30. Warchant referenced this in commit 7958da26e8 on Dec 31, 2019
31. Bushstar referenced this in commit 610b3e1b06 on Apr 8, 2020
32. KolbyML referenced this in commit 81fbb1b5f0 on Sep 4, 2020
33. MarcoFalke referenced this in commit c857148636 on May 15, 2021
34. MarcoFalke locked this on Sep 8, 2021

Contributors
gavinandresen tcatm tril0byte jhyslop

Labels
Bug