Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Sfdbi-00042a-GQ for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 20:59:02 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.175 as permitted sender) client-ip=74.125.82.175; envelope-from=grarpamp@gmail.com; helo=mail-we0-f175.google.com; Received: from mail-we0-f175.google.com ([74.125.82.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Sfdbh-0001YB-Ng for bitcoin-development@lists.sourceforge.net; Fri, 15 Jun 2012 20:59:02 +0000 Received: by werg55 with SMTP id g55so2680697wer.34 for ; Fri, 15 Jun 2012 13:58:55 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.83.168 with SMTP id r8mr7135329wiy.22.1339793935454; Fri, 15 Jun 2012 13:58:55 -0700 (PDT) Received: by 10.180.7.105 with HTTP; Fri, 15 Jun 2012 13:58:55 -0700 (PDT) Date: Fri, 15 Jun 2012 16:58:55 -0400 Message-ID: From: grarpamp To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -0.5 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (grarpamp[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 1.1 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Sfdbh-0001YB-Ng Subject: [Bitcoin-development] Manual file cleanup on exit, safe? [coredump backtrace] X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2012 20:59:02 -0000 When bitcoind exits cleanly, it does not seem safe for the blockchain to clean up the following hierarchy with rm -r ? database/ db.log .lock debug.log addr.dat wallet.dat And what about adding to the above list the following files when bitcoind crashes: __db.* Is there an option to make bitcoind roll/flush the above files on exit so they can be removed/ported? No matter the answers, bitcoind should not be dumping core. Bitcoin version v0.6.2.2-unk-beta () Default data directory /.../.bitcoin Loading addresses... dbenv.open LogDir=/.../.bitcoin/database ErrorFile=/.../.bitcoin/db.log ************************ EXCEPTION: 11DbException Db::open: Invalid argument bitcoin in AppInit() terminate called after throwing an instance of 'DbException' what(): Db::open: Invalid argument sh: abort (core dumped) file unknown has LSN 38/7968116, past end of log at 1/28 Commonly caused by moving a database from one database environment to another without clearing the database LSNs, or by removing all of the log files from a database environment __db_meta_setup: /.../.bitcoin/addr.dat: unexpected file type or format [New Thread 28801140 (LWP 100964/initial thread)] (gdb) bt #0 0x2873e9a7 in kill () from /lib/libc.so.7 #1 0x2852d397 in raise () from /lib/libthr.so.3 #2 0x2873d4da in abort () from /lib/libc.so.7 #3 0x285a0880 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #4 0x285a508a in std::set_unexpected () from /usr/lib/libstdc++.so.6 #5 0x285a50d2 in std::terminate () from /usr/lib/libstdc++.so.6 #6 0x285a4f58 in __cxa_rethrow () from /usr/lib/libstdc++.so.6 #7 0x0816d2ea in PrintException (pex=0x288251b0, pszThread=0x82f4cfa "AppInit()") at util.cpp:792 #8 0x08087625 in AppInit (argc=2, argv=0xbfbfedf0) at init.cpp:113 #9 0x0808766d in main (argc=Cannot access memory at address 0x3) at init.cpp:96