Title: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on November 26, 2012, 06:59:50 PM
Superceded with next-test 2013-04-12 (https://bitcointalk.org/?topic=175026)
next-test is a branch of the master bitcoind & Bitcoin-Qt code with as many pull requests merged as possible, to aid in testing them. This branch can be used to test many pull requests in your daily Bitcoin use. The goal is to help pull requests get the testing they need to be merged into the main tree, so once you test a change, please comment in the relevant pull request (ideally with details). Due to Coin Control's poor design and abandonment, it has begun to bitrot rapidly. This will probably be the last next-test supporting it, unless someone steps up to maintain it. Please note these might possibly corrupt your wallet. No warranty of any kind of provided. BACKUP YOUR WALLETAlso note that this is based on code that will become 0.8 including the "ultraprune" block storage rewrite. The master code does not support upgrading from older versions yet, but this next-test includes a HACKY upgrader if it detects such a condition. Note that in any case, the block chain of both your old client and this new one will be saved on your disk. That means about 5 GB for the old one and about 5 GB for the new one (unless your OS supports hard links, which the HACK will use if possible). Wallet is currently considered to be forward and backward compatible, but please still back it up!- Windows: installer (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20121125/bitcoin-next-test-20121125-win32-setup.exe) ‖ zip (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20121125/bitcoin-next-test-20121125-win32.zip) (sigs (http://luke.dashjr.org/programs/bitcoin/files/bitcoind/next/test/20121125/SHA256SUMS.asc))
- Source code: git (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/shortlog/refs/tags/next-test_20121125) ‖ tar.gz (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/snapshot/next-test_20121125.tar.gz) ‖ zip (http://luke.dashjr.org/programs/bitcoin/w/bitcoind/luke-jr.git/snapshot/next-test_20121125.zip)
Today's next-test includes the following pull requests (green are merged now; red are disputed): - Parse URIs with non-BTC amounts (https://github.com/bitcoin/bitcoin/pull/553)
- -acceptnonstdtxn option to skip "non-standard transaction" checks (https://github.com/bitcoin/bitcoin/pull/559)
- Support for Tonal Bitcoin units (ᵇTBC, ˢTBC, and TBC) (https://github.com/bitcoin/bitcoin/pull/929)
- Issue1234 (https://github.com/bitcoin/bitcoin/pull/1271)
- Who doctored.... never was very useful, now only for the debuggers... (https://github.com/bitcoin/bitcoin/pull/1339)
- getblocktemplate: longpolling support (https://github.com/bitcoin/bitcoin/pull/1355)
- Coin Control (https://github.com/bitcoin/bitcoin/pull/1359)
- Show how long AcceptBlock() takes to process. (https://github.com/bitcoin/bitcoin/pull/1377)
- Add new P2P command and response: "getcmds", "cmdlist" (https://github.com/bitcoin/bitcoin/pull/1471)
- improve dust spamming prevention algorithm (https://github.com/bitcoin/bitcoin/pull/1536)
- RPC: Add per-message statistics to 'getpeerinfo' (https://github.com/bitcoin/bitcoin/pull/1538)
- Addnode optimization and addnode access via RPC (https://github.com/bitcoin/bitcoin/pull/1549)
- JSON-RPC method: prioritisetransaction <txid> <priority delta> (https://github.com/bitcoin/bitcoin/pull/1583)
- A set of build scripts on top of gitian and vagrant for automating gitian builds... (https://github.com/bitcoin/bitcoin/pull/1597)
- Change window titles to "Bitcoin-Qt - <purpose>" / misc related renames (https://github.com/bitcoin/bitcoin/pull/1620)
- Specify fees explicitly via JSON-RPC (https://github.com/bitcoin/bitcoin/pull/1645)
- CreateNewBlock: Child-pays-for-parent / Add transaction fee later (https://github.com/bitcoin/bitcoin/pull/1647)
- Relay and accept transactions that personally benefit the user (https://github.com/bitcoin/bitcoin/pull/1648)
- Bitcoin-Qt: add a Reset button to the options dialog (https://github.com/bitcoin/bitcoin/pull/1685)
- enhance proxy support / network init (https://github.com/bitcoin/bitcoin/pull/1781)
- Replace ThreadDumpAddresses with a timer. (https://github.com/bitcoin/bitcoin/pull/1787)
- Bloom filters (https://github.com/bitcoin/bitcoin/pull/1795)
- Add small-data OP_DROP transactions as standard transactions. (https://github.com/bitcoin/bitcoin/pull/1809)
- FreeBSD and OpenBSD build fixes (https://github.com/bitcoin/bitcoin/pull/1815)
- Support for specific BIP 22 rejection reasons and BIP 23 block proposal (https://github.com/bitcoin/bitcoin/pull/1816)
- Base58 en-/de-coding (https://github.com/bitcoin/bitcoin/pull/1828)
- Fixes for when listtransactions encounters non-standard outputs (https://github.com/bitcoin/bitcoin/pull/1850)
- Add new RPC "lockunspent", to prevent spending of selected outputs (https://github.com/bitcoin/bitcoin/pull/1861)
- In listaddressgroupings push down the IsMine check to run on each input. (https://github.com/bitcoin/bitcoin/pull/1872)
- let user select wallet file with -wallet=foo.dat (https://github.com/bitcoin/bitcoin/pull/1889)
- Add NATIVE_WINDOWS (https://github.com/bitcoin/bitcoin/pull/1940)
- Add signfile/verifyfile RPC calls. (https://github.com/bitcoin/bitcoin/pull/1957)
- Add -walletnotify to call an external script on wallet transactions (https://github.com/bitcoin/bitcoin/pull/1974)
- Add wget(1)-friendly crypted key dump via GET /wallet-ckeys.json (https://github.com/bitcoin/bitcoin/pull/1982)
- Normalize wallet RPC commands (refillkeypool, unlockwallet, lockwallet, setpassphrase) (https://github.com/bitcoin/bitcoin/pull/1983)
- RPC: Avoid cleartext passwords by default (https://github.com/bitcoin/bitcoin/pull/1986)
- update CClientUIInterface and remove orphan Wx stuff (https://github.com/bitcoin/bitcoin/pull/1988)
- Documented locking part 1+2 (https://github.com/bitcoin/bitcoin/pull/2003)
- Change 'make' to $(MAKE) in leveldb make command line (https://github.com/bitcoin/bitcoin/pull/2006)
- Restore FIRST_CLASS_MESSAGING (https://github.com/bitcoin/bitcoin/pull/2014)
- P2P: parse network datastream into header/data components in socket thread (https://github.com/bitcoin/bitcoin/pull/2016)
- P2P: improve RX/TX flow control (https://github.com/bitcoin/bitcoin/pull/2017)
- reformat OS X build instrcs, add 10.8 + Homebrew (https://github.com/bitcoin/bitcoin/pull/2026)
- Deploy properly with Nokia Qt installer's Frameworks on OSX (https://github.com/bitcoin/bitcoin/pull/2030)
- Fix duplicate shortcut usage in sign/verify message dialog. (https://github.com/bitcoin/bitcoin/pull/2032)
- Bugfix: remove conflicting transactions from memory pool (https://github.com/bitcoin/bitcoin/pull/2033)
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: hazek on November 26, 2012, 11:14:44 PM
8min for 30% synchronization, was this always this fast? :D
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on November 26, 2012, 11:16:18 PM
8min for 30% synchronization, was this always this fast? :D No, that's a combination of ultraprune and the upgrade hack...
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: hazek on November 26, 2012, 11:22:33 PM
and the upgrade hack...
Does that affect me if I'm doing a fresh install? I didn't have QT or the blockchain on my HDD before. EDIT: ~50% = ~20min EDIT2: ~60% = ~35min EDIT3: :/ it really slowed down now, ~62.5% = ~60min EDIT4: ~66.5% = ~90min EDIT5: ~75% = ~110min EDIT6: ~85.5% = ~130min taking up 800mb of my ram and from time to time really slowing down my laptop EDIT8: Well I fked it up. I foolishly started to play around with QT and encrypted the wallet which I didn't know would prompt a restart and so I lost connection with 50 peers and probably some time before I get those back. ~87,5% = ~150min EDIT9: ~88.5% = ~180min EDIT10: ~91.5% = ~210min EDIT11: ~92.5% = ~230min For some reason the system is becoming unresponsive every 30seconds or so for a couple of seconds, and my laptop really should be able to handle this without breaking a sweat. EDIT12: woke up to a crashed QT, when I ran it again it showed ~96% = ~640min EDIT13: ~98% = ~700min EDIT14: 100% = ~740min and this is with 1 restart and 1 crash
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: prezbo on November 26, 2012, 11:25:40 PM
8min for 30% synchronization, was this always this fast? :D
I thought this was going to be synchronized in no time. Then at around 15k to go it almost slowed down to a halt.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Bitexchange on November 26, 2012, 11:40:53 PM
let user select wallet file with -wallet=foo.dat gmaxwell commented 2 months ago
Eh. The functionality is desirable, but the ability to filesystem split the wallet and data dir is a surefire way to end up with a corrupted wallet. This is subtle and I suspect hard to warn people out of doing, esp since it would mostly work. (until it eats your keys for lunch).
Whats the problem with using multiple wallet files with the same bitcoin client? Ok you could miss recieved coins if you update the blockchain when there is the wrong wallet loaded, but if you make sure that doesnt happen, is there any technical reason why i cant make 10 wallets and load them when needed? Because im already doing that and didnt have any problem so far ;)
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Pieter Wuille on November 26, 2012, 11:46:43 PM
Whats the problem with using multiple wallet files with the same bitcoin client?
None at all, it just isn't implemented. What is a problem, is separating the wallet and the database environment. If your client (or your computer) crashes, you must have the database environment (the files in $DATADIR/database) to recover the data. If those are not available, the wallet may get corrupted. BDB isn't really intended to be used with free-floating database files - it expects them to be part of such an environment. Now, we are slowly moving away from BDB. 0.8 (and this next-test build) do not use it anymore for the block chain indexes (it uses LevelDB instead), and we'll likely stop using BDB for wallet files as well. At that point, it will be perfectly safe to select any file/location for your wallet.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on November 26, 2012, 11:47:30 PM
let user select wallet file with -wallet=foo.dat gmaxwell commented 2 months ago
Eh. The functionality is desirable, but the ability to filesystem split the wallet and data dir is a surefire way to end up with a corrupted wallet. This is subtle and I suspect hard to warn people out of doing, esp since it would mostly work. (until it eats your keys for lunch).
Whats the problem with using multiple wallet files with the same bitcoin client? Ok you could miss recieved coins if you update the blockchain when there is the wrong wallet loaded, but if you make sure that doesnt happen, is there any technical reason why i cant make 10 wallets and load them when needed? Because im already doing that and didnt have any problem so far ;) You won't even miss received coins since the client automatically detects when it needs to rescan. The problem gmaxwell mentions is only if you do something stupid like -wallet=/mnt/usbdrive/wallet.dat, since the database/ directory it depends on is still on the main hard drive. So long as you keep all your wallets on the same disk it should be fine.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Bitexchange on November 27, 2012, 12:20:30 AM
Ok nice, didnt know that, thanks.
So the wallet.dat contains puplic/private keys, transactions, and the block count where it got all previous transactions ?
If i didnt use a wallet for some time, it will rescan the blockchain i got on my disk without downloading it again? Is there any status shown on the client which tells me if the wallet is up to date with the blockchain dat files?
Because i didnt really notice something like that so i guessed its better not to recieve coins on wallets which arent currently 'loaded' while updating the blockchain with another wallet.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: hazek on November 27, 2012, 12:58:51 AM
Is it normal for QT to take up 900mb of ram?
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Vitalik Buterin on November 27, 2012, 03:17:48 PM
Make on Linux (Xubuntu) does not work without libminiupnpc8-dev installed.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Dezeer on November 27, 2012, 03:41:00 PM
Indexing advanced rapidly, 50 blocks per second, into the remaining 17000-16800 and its now indexing at pace one per second. Memory usage is at this point, before indexing has completed, normal at 150MB.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on November 27, 2012, 10:07:31 PM
Make on Linux (Xubuntu) does not work without libminiupnpc8-dev installed. You mean with USE_UPNP=- (don't compile support)?
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: rabit on November 27, 2012, 10:20:36 PM
Make on Linux (Xubuntu) does not work without libminiupnpc8-dev installed. You mean with USE_UPNP=- (don't compile support)? Its set to USE_UPNP=- in line 41 of makefile.unix .
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on November 27, 2012, 10:26:01 PM
Make on Linux (Xubuntu) does not work without libminiupnpc8-dev installed. You mean with USE_UPNP=- (don't compile support)? Its set to USE_UPNP=- in line 41 of makefile.unix . No, it's set by default to USE_UPNP=0 (compile support, but disable by default) on line 5, and changed from (null) to - on line 41. So eg, USE_UPNP= will work also (but there is no way to support this syntax with -Qt)
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: rabit on November 27, 2012, 10:41:15 PM
Make on Linux (Xubuntu) does not work without libminiupnpc8-dev installed. You mean with USE_UPNP=- (don't compile support)? Its set to USE_UPNP=- in line 41 of makefile.unix . No, it's set by default to USE_UPNP=0 (compile support, but disable by default) on line 5, and changed from (null) to - on line 41. So eg, USE_UPNP= will work also (but there is no way to support this syntax with -Qt) The problem is that the README states that libminiupnpc is optional but make -f makefile.unix doesnt work without it, so maybe the default setting should be USE_UPNP=-. But probably its not that important.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on November 27, 2012, 10:44:28 PM
Make on Linux (Xubuntu) does not work without libminiupnpc8-dev installed. You mean with USE_UPNP=- (don't compile support)? Its set to USE_UPNP=- in line 41 of makefile.unix . No, it's set by default to USE_UPNP=0 (compile support, but disable by default) on line 5, and changed from (null) to - on line 41. So eg, USE_UPNP= will work also (but there is no way to support this syntax with -Qt) The problem is that the README states that libminiupnpc is optional but make -f makefile.unix doesnt work without it, so maybe the default setting should be USE_UPNP=-. But probably its not that important. And immediately under the dependency list: miniupnpc may be used for UPnP port mapping. It can be downloaded from
http://miniupnp.tuxfamily.org/files/. UPnP support is compiled in and
turned off by default. Set USE_UPNP to a different value to control this:
USE_UPNP=- No UPnP support - miniupnp not required
USE_UPNP=0 (the default) UPnP support turned off by default at runtime
USE_UPNP=1 UPnP support turned on by default at runtime This isn't something new either, it's been this way since 0.4
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: dust on November 28, 2012, 06:16:17 AM
8min for 30% synchronization, was this always this fast? :D
I thought this was going to be synchronized in no time. Then at around 15k to go it almost slowed down to a halt. There are very few transactions in the first 30% of blocks, so these blocks download and verify very quickly. The most recent 15k transactions have a bunch of transactions (many of them satoshidice related), which makes them slower to process.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Pieter Wuille on November 28, 2012, 08:21:46 AM
Indexing advanced rapidly, 50 blocks per second, into the remaining 17000-16800 and its now indexing at pace one per second. Memory usage is at this point, before indexing has completed, normal at 150MB.
After the last checkpoint (block 193000 currently), signature verification is enabled, and in all likelyhood this is the bottleneck after that point.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Pieter Wuille on November 28, 2012, 08:23:40 AM
So the wallet.dat contains puplic/private keys, transactions, and the block count where it got all previous transactions ?
Yes, since 0.3.21. If i didnt use a wallet for some time, it will rescan the blockchain i got on my disk without downloading it again? Is there any status shown on the client which tells me if the wallet is up to date with the blockchain dat files?
Yes, it will. It does this rescan automatically at startup, so there is no feedback in the GUI - when it is loaded, the wallet should always be up-to-date with the block chain.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Pieter Wuille on November 28, 2012, 08:25:31 AM
Is it normal for QT to take up 900mb of ram?
No (unless you're just talking about virtual memory). What OS are you on? Your earlier post makes me think there is some memory leak or resource leak of some kind (locks in LevelDB maybe).
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: hazek on November 28, 2012, 11:22:19 AM
Is it normal for QT to take up 900mb of ram?
No (unless you're just talking about virtual memory). What OS are you on? Your earlier post makes me think there is some memory leak or resource leak of some kind (locks in LevelDB maybe). Win7 64bit, I was talking actual RAM, it's ok now, it takes up around 180mb but during the blockchain download it went up to 918 then later on hovered around 700 and it crashed before I woke up. After the crash it didn't seem to ever go that high again so I have no idea.. Would you like my log file?
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Nachtwind on November 28, 2012, 08:47:56 PM
One thing that strikes me every time i see the testing stuff is: Why the hell is there "Tonal" (still) in it?
Honestly.. there must be like 4 or 5 people - world wide - who use that. Possible that a large percentage of those use Bitcoin, but why keep that stuff?
The world becomes more and more metric - take a look at sciences - and why should something like bitcoin be that resilient to give up on such useless stuff as tonal?
Other than that: Nice testing... syncing is as fast/slow as expected..
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: rabit on November 28, 2012, 09:14:08 PM
At the beginning bitcoind worked for me without any issuses but now i get the following error at start:
Error: Failed to connect best block
debug.log:
...
ERROR: CheckProofOfWork() : nBits below minimum work
ERROR: CBlock::ReadFromDisk() : errors in block header
ERROR: SetBestBlock() : ReadFromDisk for connect failed
Loading addresses...
...
Done loading
: Failed to connect best block
...
socket send error 9
...
Error; StartDumpAddressTimer() failed
...
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: notme on November 28, 2012, 09:28:59 PM
One thing that strikes me every time i see the testing stuff is: Why the hell is there "Tonal" (still) in it?
Honestly.. there must be like 4 or 5 people - world wide - who use that. Possible that a large percentage of those use Bitcoin, but why keep that stuff?
The world becomes more and more metric - take a look at sciences - and why should something like bitcoin be that resilient to give up on such useless stuff as tonal?
Other than that: Nice testing... syncing is as fast/slow as expected..
Because OP is obsessed with tonal.
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: FooBaer on November 30, 2012, 07:54:51 PM
Just some performance notes:
First start with an .bitcoin directory from the stock 0.7.1 client:
The "Reindexing blocks on disk"-task went to ~90% quite fast (about 5min), than come nearly to an halt. About one block per 5-10sec.
After restarting the app it started a bit faster for ~100..200 blocks but slowed down again to 1block per 5sec (some are faster). Is still reindexing. About 16000 blocks remaining.
OS: Ubuntu 12.10, Notebook, normal harddisk (non SSD); CPU: one core is saturated with bitcoin-qt
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Pieter Wuille on November 30, 2012, 07:59:31 PM
The first 193000 blocks should go much faster than the rest, that is normal. Before the last checkpoint, signatures are not verified.
One block per 5-10 seconds sounds slow. What kind of CPU/RAM are you on?
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: FooBaer on November 30, 2012, 09:08:07 PM
I left my notebook alone for one hour; now, 1h10min later I am on 13800 blocks reamaining -> 2200 Blocks in 4200sec -> ~2sec per Block.
At the current rate, ETA is 7.6h
I have:
Intel(R) Pentium(R) Dual CPU T2390 @ 1.86GHz
2GiB notebookram (dont know the frequency)
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: FooBaer on November 30, 2012, 10:12:10 PM
Okay, now it coredumped.... After resarting the application it continued to "Reindexing blocks on disk" at 11600 blocks remaining. Rest (Transaktions, Addresses) is looking fine. This is the output on the console - is there any other debug log? /bitcoin-qt
*** glibc detected *** ./bitcoin-qt: double free or corruption (fasttop): 0xb2405cb8 ***
======= Backtrace: =========
/lib/i386-linux-gnu/libc.so.6(+0x75ee2)[0xb631dee2]
/usr/lib/i386-linux-gnu/libstdc++.so.6(_ZdlPv+0x1f)[0xb64e4adf]
./bitcoin-qt[0x811dbfe]
./bitcoin-qt[0x81613bb]
./bitcoin-qt[0x815cdd8]
./bitcoin-qt[0x815dbef]
/usr/lib/libboost_thread.so.1.49.0(+0xb95c)[0xb735e95c]
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb733ed4c]
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb6396d3e]
======= Memory map: ========
08048000-085ec000 r-xp 00000000 08:07 1584334 /home/daniel/src/bitcoin_luke-jr-pre08/bitcoin-qt
085ec000-085ed000 r--p 005a4000 08:07 1584334 /home/daniel/src/bitcoin_luke-jr-pre08/bitcoin-qt
085ed000-085ef000 rw-p 005a5000 08:07 1584334 /home/daniel/src/bitcoin_luke-jr-pre08/bitcoin-qt
085ef000-085f1000 rw-p 00000000 00:00 0
08b5b000-0ca01000 rw-p 00000000 00:00 0 [heap]
a0bd6000-a1acb000 rw-p 00000000 00:00 0
a27e3000-a2f61000 rw-p 00000000 00:00 0
a3100000-a3122000 rw-p 00000000 00:00 0
a3122000-a3200000 ---p 00000000 00:00 0
a3300000-a3400000 rw-p 00000000 00:00 0
a3500000-a3700000 rw-p 00000000 00:00 0
a3700000-a37fd000 rw-p 00000000 00:00 0
a37fd000-a3800000 ---p 00000000 00:00 0
a3800000-a3900000 rw-p 00000000 00:00 0
a3900000-a3b00000 rw-p 00000000 00:00 0
a3b00000-a3d00000 rw-p 00000000 00:00 0
a3d00000-a3f00000 rw-p 00000000 00:00 0
a3f00000-a4100000 rw-p 00000000 00:00 0
a4100000-a4300000 rw-p 00000000 00:00 0
a4300000-a4500000 rw-p 00000000 00:00 0
a4500000-a46ff000 rw-p 00000000 00:00 0
a46ff000-a4700000 ---p 00000000 00:00 0
a4700000-a4900000 rw-p 00000000 00:00 0
a4900000-a4b00000 rw-p 00000000 00:00 0
a4b00000-a4d00000 rw-p 00000000 00:00 0
a4d00000-a4f00000 rw-p 00000000 00:00 0
a4f00000-a5100000 rw-p 00000000 00:00 0
a5100000-a52fa000 rw-p 00000000 00:00 0
a52fa000-a5300000 ---p 00000000 00:00 0
a5300000-a5500000 rw-p 00000000 00:00 0
a5500000-a5700000 rw-p 00000000 00:00 0
a5700000-a58ff000 rw-p 00000000 00:00 0
a58ff000-a5900000 ---p 00000000 00:00 0
a5900000-a5a00000 rw-p 00000000 00:00 0
a5a00000-a5b00000 rw-s 003f0000 08:07 23594305 /home/daniel/.bitcoin/coins/010251.log
a5b00000-a5d00000 rw-p 00000000 00:00 0
a5d00000-a5f00000 rw-p 00000000 00:00 0
a5f00000-a6100000 rw-p 00000000 00:00 0
a6100000-a6200000 rw-p 00000000 00:00 0
a62d1000-a6331000 rw-s 00000000 00:04 2129927 /SYSV00000000 (deleted)
a6331000-a6337000 r--p 00000000 08:05 1450622 /usr/share/locale-langpack/de/LC_MESSAGES/gdk-pixbuf.mo
a6337000-a6500000 rw-s 00000000 00:04 2097158 /SYSV00000000 (deleted)
a6500000-a6700000 rw-p 00000000 00:00 0
a6700000-a6800000 rw-p 00000000 00:00 0
a68f8000-a68f9000 ---p 00000000 00:00 0
a68f9000-a70f9000 rw-p 00000000 00:00 0 [stack:17567]
a70f9000-a70fa000 ---p 00000000 00:00 0
a70fa000-a78fa000 rw-p 00000000 00:00 0 [stack:17566]
a78fa000-a78fb000 ---p 00000000 00:00 0
a78fb000-a80fb000 rw-p 00000000 00:00 0 [stack:17565]
a80fb000-a80fc000 ---p 00000000 00:00 0
a80fc000-a88fc000 rw-p 00000000 00:00 0 [stack:17564]
a88fc000-a88fd000 ---p 00000000 00:00 0
a88fd000-a90fd000 rw-p 00000000 00:00 0
a90fd000-a90fe000 ---p 00000000 00:00 0
a90fe000-a98fe000 rw-p 00000000 00:00 0 [stack:17562]
a98fe000-a98ff000 ---p 00000000 00:00 0
a98ff000-aa0ff000 rw-p 00000000 00:00 0
aa0ff000-aa100000 ---p 00000000 00:00 0
aa100000-aa900000 rw-p 00000000 00:00 0 [stack:17569]
aa900000-aa9ff000 rw-p 00000000 00:00 0
aa9ff000-aaa00000 ---p 00000000 00:00 0
aaa12000-aaa13000 ---p 00000000 00:00 0
aaa13000-ab3fc000 rw-p 00000000 00:00 0
ab5b0000-ab5c0000 rw-s 00000000 08:07 23594302 /home/daniel/.bitcoin/blktree/000467.log
ab5c0000-ab5c1000 ---p 00000000 00:00 0
ab5c1000-abdc2000 rw-p 00000000 00:00 0 [stack:17557]
abdc2000-abdc3000 ---p 00000000 00:00 0
abdc3000-ac5c3000 rw-p 00000000 00:00 0 [stack:17555]
ac5c3000-ac5d3000 rw-s 00000000 08:07 23594379 /home/daniel/.bitcoin/blktree/MANIFEST-000453
ac5d3000-ad300000 rw-p 00000000 00:00 0
ad300000-ad3f9000 rw-p 00000000 00:00 0
ad3f9000-ad400000 ---p 00000000 00:00 0
ad418000-ad458000 rw-s 00030000 08:07 23594401 /home/daniel/.bitcoin/coins/MANIFEST-007748
ad458000-ad459000 ---p 00000000 00:00 0
ad459000-adc59000 rw-p 00000000 00:00 0 [stack:17554]
adc59000-adcb8000 r--p 00000000 08:05 1702905 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-RI.ttf
adcb8000-adcd7000 rw-s 00000000 00:04 2064389 /SYSV00000000 (deleted)
adcd7000-addf0000 r--p 00000000 08:05 1708811 /usr/share/fonts/truetype/unfonts-core/UnGraphicBold.ttf
addf0000-ade05000 r--p 00000000 08:05 1704551 /usr/share/fonts/truetype/ttf-indic-fonts-core/Rekha.ttf
ade05000-ade17000 r--p 00000000 08:05 1704553 /usr/share/fonts/truetype/ttf-indic-fonts-core/gargi.ttf
ade17000-ade33000 r--p 00000000 08:05 1705278 /usr/share/fonts/truetype/liberation/LiberationSansNarrow-Regular.ttf
ade33000-ade3d000 r--p 00000000 08:05 1715948 /usr/share/fonts/type1/mathml/Symbol.pfb
ade3d000-adf5a000 r--p 00000000 08:05 1708876 /usr/share/fonts/truetype/unfonts-core/UnGraphic.ttf
adf5a000-ae53a000 r--p 00000000 08:05 1707030 /usr/share/fonts/truetype/unfonts-core/UnBatang.ttf
ae53a000-aea48000 r--p 00000000 08:05 1701151 /usr/share/fonts/truetype/droid/DroidSansFallbackFull.ttf
aea48000-aef39000 r--p 00000000 08:05 1705106 /usr/share/fonts/truetype/wqy/wqy-microhei.ttc
aef39000-aef52000 r--p 00000000 08:05 1704543 /usr/share/fonts/truetype/ttf-indic-fonts-core/Kedage-n.ttf
aef52000-aef5a000 r--p 00000000 08:07 23724664 /home/daniel/.fonts/a/ahem.ttf
aef5a000-aef6f000 r--p 00000000 08:05 1704504 /usr/share/fonts/truetype/tlwg/Sawasdee.ttf
aef6f000-aeffd000 r--p 00000000 08:05 1702347 /usr/share/fonts/truetype/abyssinica/AbyssinicaSIL-R.ttf
aeffd000-af02d000 r--p 00000000 08:05 1704549 /usr/share/fonts/truetype/ttf-indic-fonts-core/Pothana2000.ttf
af02d000-af47b000 r--p 00000000 08:05 1704531 /usr/share/fonts/truetype/tibetan-machine/TibetanMachineUni.ttf
af47b000-af81d000 r--p 00000000 08:05 1704447 /usr/share/fonts/truetype/nanum/NanumMyeongjo.ttf
af81d000-af876000 r--p 00000000 08:05 1702765 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf
af876000-af8c8000 r--p 00000000 08:05 1701491 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf
af8c8000-af93d000 r--p 00000000 08:05 1702641 /usr/share/fonts/truetype/padauk/Padauk-book.ttf
af93d000-af987000 r--p 00000000 08:05 1589407 /usr/share/fonts/truetype/msttcorefonts/Courier_New.ttf
af987000-aff7a000 r--p 00000000 08:05 1704481 /usr/share/fonts/truetype/takao-gothic/TakaoPGothic.ttf
aff7a000-affd8000 r--p 00000000 08:05 1704550 /usr/share/fonts/truetype/ttf-indic-fonts-core/Rachana_04.ttf
affd8000-afff2000 r--p 00000000 08:05 1704495 /usr/share/fonts/truetype/tlwg/Norasi.ttf
afff2000-affff000 r--p 00000000 08:05 1704443 /usr/share/fonts/truetype/kacst-one/KacstOne.ttf
affff000-b046f000 r--p 00000000 08:05 1706095 /usr/share/fonts/truetype/horai-umefont/ume-pgc4.ttf
b046f000-b04a1000 r--p 00000000 08:05 1700617 /usr/share/fonts/truetype/openoffice/opens___.ttf
b04a1000-b07c8000 r--p 00000000 08:05 1703355 /usr/share/fonts/truetype/freefont/FreeSerif.ttf
b07c8000-b0859000 r--p 00000000 08:05 1703360 /usr/share/fonts/truetype/freefont/FreeMono.ttf
b0859000-b09d7000 r--p 00000000 08:05 1703001 /usr/share/fonts/truetype/freefont/FreeSans.ttf
b09d7000-b0a22000 r--p 00000000 08:05 1701290 /usr/share/fonts/truetype/sinhala/lklug.ttf
b0a22000-b0a74000 r--p 00000000 08:05 1704546 /usr/share/fonts/truetype/ttf-indic-fonts-core/Meera_04.ttf
b0a74000-b0a88000 r--p 00000000 08:05 1704556 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_hi.ttf
b0a88000-b0a9c000 r--p 00000000 08:05 1704555 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_gu.ttf
b0a9c000-b0abf000 r--p 00000000 08:05 1704554 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_bn.ttf
b0abf000-b0ea7000 r--p 00000000 08:05 1704534 /usr/share/fonts/truetype/unfonts-core/UnDotumBold.ttf
b0ea7000-b1224000 r--p 00000000 08:05 1704533 /usr/share/fonts/truetype/unfonts-core/UnDotum.ttf
b1224000-b1649000 r--p 00000000 08:05 1704444 /usr/share/fonts/truetype/nanum/NanumGothic.ttf
b1649000-b1677000 r--p 00000000 08:05 1704547 /usr/share/fonts/truetype/ttf-indic-fonts-core/MuktiNarrow.ttf
b1677000-b16b8000 r--p 00000000 08:05 1704559 /usr/share/fonts/truetype/ttf-khmeros-core/KhmerOS.ttf
b16b8000-b16ce000 r--p 00000000 08:05 1704528 /usr/share/fonts/truetype/tlwg/Waree.ttf
b16ce000-b16e2000 r--p 00000000 08:05 1704619 /usr/share/fonts/type1/gsfonts/n019003l.pfb
b16e2000-b1726000 r--p 00000000 08:05 1589403 /usr/share/fonts/truetype/msttcorefonts/Arial.ttf
b1726000-b1749000 r--p 00000000 08:05 1590476 /usr/share/fonts/truetype/msttcorefonts/Verdana.ttf
b1749000-b17ee000 r--p 00000000 08:05 1701489 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf
b17ee000-b189e000 r--p 00000000 08:05 1701283 /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf
b189e000-b18f0000 r--p 00000000 08:05 1702780 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-B.ttf
b18f0000-b1947000 r--p 00000000 08:05 1702838 /usr/share/fonts/truetype/ubuntu-font-family/Ubuntu-R.ttf
b1947000-b1978000 r-xp 00000000 08:05 1177387 /usr/lib/i386-linux-gnu/libdbusmenu-qt.so.2.6.0
b1978000-b1979000 r--p 00031000 08:05 1177387 /usr/lib/i386-linux-gnu/libdbusmenu-qt.so.2.6.0
b1979000-b197a000 rw-p 00032000 08:05 1177387 /usr/lib/i386-linux-gnu/libdbusmenu-qt.so.2.6.0
b197a000-b19bb000 rw-p 00000000 00:00 0
b19ca000-b19db000 r--p 00000000 08:05 1704557 /usr/share/fonts/truetype/ttf-indic-fonts-core/lohit_ta.ttf
b19db000-b19fa000 r-xp 00000000 08:05 1178285 /usr/lib/i386-linux-gnu/qt4/plugins/systemtrayicon/libsni-qt.so
b19fa000-b19fb000 r--p 0001e000 08:05 1178285 /usr/lib/i386-linux-gnu/qt4/plugins/systemtrayicon/libsni-qt.so
b19fb000-b19fc000 rw-p 0001f000 08:05 1178285 /usr/lib/i386-linux-gnu/qt4/plugins/systemtrayicon/libsni-qt.so
b19fc000-b1a07000 r-xp 00000000 08:05 1182305 /usr/lib/i386-linux-gnu/libjbig.so.0.0.0
b1a07000-b1a08000 r--p 0000a000 08:05 1182305 /usr/lib/i386-linux-gnu/libjbig.so.0.0.0
b1a08000-b1a0b000 rw-p 0000b000 08:05 1182305 /usr/lib/i386-linux-gnu/libjbig.so.0.0.0
b1a0b000-b1a7a000 r-xp 00000000 08:05 1177526 /usr/lib/i386-linux-gnu/libtiff.so.5.1.0
b1a7a000-b1a7b000 ---p 0006f000 08:05 1177526 /usr/lib/i386-linux-gnu/libtiff.so.5.1.0
b1a7b000-b1a7c000 r--p 0006f000 08:05 1177526 /usr/lib/i386-linux-gnu/libtiff.so.5.1.0
b1a7c000-b1a7e000 rw-p 00070000 08:05 1177526 /usr/lib/i386-linux-gnu/libtiff.so.5.1.0
b1a7e000-b1ad0000 r-xp 00000000 08:05 1179566 /usr/lib/i386-linux-gnu/libQtSvg.so.4.8.3
b1ad0000-b1ad1000 ---p 00052000 08:05 1179566 /usr/lib/i386-linux-gnu/libQtSvg.so.4.8.3
b1ad1000-b1ad2000 r--p 00052000 08:05 1179566 /usr/lib/i386-linux-gnu/libQtSvg.so.4.8.3
b1ad2000-b1ad3000 rw-p 00053000 08:05 1179566 /usr/lib/i386-linux-gnu/libQtSvg.so.4.8.3
b1ad5000-b1ada000 r-xp 00000000 08:05 663600 /lib/i386-linux-gnu/libnss_dns-2.15.so
b1ada000-b1adb000 r--p 00004000 08:05 663600 /lib/i386-linux-gnu/libnss_dns-2.15.so
b1adb000-b1adc000 rw-p 00005000 08:05 663600 /lib/i386-linux-gnu/libnss_dns-2.15.so
b1adc000-b1aec000 r-xp 00000000 08:05 1177853 /usr/lib/i386-linux-gnu/qt4/plugins/menubar/libappmenu-qt.so
b1aec000-b1aed000 r--p 0000f000 08:05 1177853 /usr/lib/i386-linux-gnu/qt4/plugins/menubar/libappmenu-qt.so
b1aed000-b1aee000 rw-p 00010000 08:05 1177853 /usr/lib/i386-linux-gnu/qt4/plugins/menubar/libappmenu-qt.so
b1aee000-b1b24000 r-xp 00000000 08:05 1181993 /usr/lib/i386-linux-gnu/liblcms.so.1.0.19
b1b24000-b1b25000 r--p 00035000 08:05 1181993 /usr/lib/i386-linux-gnu/liblcms.so.1.0.19
b1b25000-b1b26000 rw-p 00036000 08:05 1181993 /usr/lib/i386-linux-gnu/liblcms.so.1.0.19
b1b26000-b1b28000 rw-p 00000000 00:00 0
b1b28000-b1ba8000 r-xp 00000000 08:05 1182267 /usr/lib/i386-linux-gnu/libmng.so.1.1.0.10
b1ba8000-b1baa000 r--p 0007f000 08:05 1182267 /usr/lib/i386-linux-gnu/libmng.so.1.1.0.10
b1baa000-b1bab000 rw-p 00081000 08:05 1182267 /usr/lib/i386-linux-gnu/libmng.so.1.1.0.10
b1bb0000-b1bb7000 r--p 00000000 08:05 1704562 /usr/share/fonts/truetype/ttf-punjabi-fonts/lohit_pa.ttf
b1bb7000-b1bbe000 r-xp 00000000 08:05 1180405 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqtiff.so
b1bbe000-b1bbf000 r--p 00006000 08:05 1180405 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqtiff.so
b1bbf000-b1bc0000 rw-p 00007000 08:05 1180405 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqtiff.so
b1bc0000-b1bc4000 r-xp 00000000 08:05 1179919 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqsvg.so
b1bc4000-b1bc5000 r--p 00004000 08:05 1179919 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqsvg.so
b1bc5000-b1bc6000 rw-p 00005000 08:05 1179919 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqsvg.so
b1bc6000-b1bcb000 r-xp 00000000 08:05 1181308 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqmng.so
b1bcb000-b1bcc000 r--p 00004000 08:05 1181308 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqmng.so
b1bcc000-b1bcd000 rw-p 00005000 08:05 1181308 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqmng.so
b1bcd000-b1bd4000 r-xp 00000000 08:05 1181214 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqjpeg.so
b1bd4000-b1bd5000 r--p 00006000 08:05 1181214 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqjpeg.so
b1bd5000-b1bd6000 rw-p 00007000 08:05 1181214 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqjpeg.so
b1bd6000-b1bdd000 r-xp 00000000 08:05 1181397 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqico.so
b1bdd000-b1bde000 r--p 00006000 08:05 1181397 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqico.so
b1bde000-b1bdf000 rw-p 00007000 08:05 1181397 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqico.so
b1bdf000-b1be5000 r-xp 00000000 08:05 1181398 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqgif.so
b1be5000-b1be6000 r--p 00005000 08:05 1181398 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqgif.so
b1be6000-b1be7000 rw-p 00006000 08:05 1181398 /usr/lib/i386-linux-gnu/qt4/plugins/imageformats/libqgif.so
b1be7000-b1beb000 r-xp 00000000 08:05 1196122 /usr/lib/kde4/plugins/imageformats/kimg_xview.so
b1beb000-b1bec000 r--p 00003000 08:05 1196122 /usr/lib/kde4/plugins/imageformats/kimg_xview.so
b1bec000-b1bed000 rw-p 00004000 08:05 1196122 /usr/lib/kde4/plugins/imageformats/kimg_xview.so
b1bed000-b1bfc000 r-xp 00000000 08:05 1196115 /usr/lib/kde4/plugins/imageformats/kimg_xcf.so
b1bfc000-b1bfd000 r--p 0000e000 08:05 1196115 /usr/lib/kde4/plugins/imageformats/kimg_xcf.so
b1bfd000-b1bfe000 rw-p 0000f000 08:05 1196115 /usr/lib/kde4/plugins/imageformats/kimg_xcf.so
b1bfe000-b1c02000 rw-p 00000000 00:00 0
b1c02000-b1c07000 r-xp 00000000 08:05 1196121 /usr/lib/kde4/plugins/imageformats/kimg_tga.so
b1c07000-b1c08000 r--p 00004000 08:05 1196121 /usr/lib/kde4/plugins/imageformats/kimg_tga.so
b1c08000-b1c09000 rw-p 00005000 08:05 1196121 /usr/lib/kde4/plugins/imageformats/kimg_tga.so
b1c09000-b1c12000 r-xp 00000000 08:05 1196116 /usr/lib/kde4/plugins/imageformats/kimg_rgb.so
b1c12000-b1c13000 r--p 00008000 08:05 1196116 /usr/lib/kde4/plugins/imageformats/kimg_rgb.so
b1c13000-b1c14000 rw-p 00009000 08:05 1196116 /usr/lib/kde4/plugins/imageformats/kimg_rgb.so
b1c14000-b1c19000 r-xp 00000000 08:05 1196117 /usr/lib/kde4/plugins/imageformats/kimg_ras.so
b1c19000-b1c1a000 r--p 00004000 08:05 1196117 /usr/lib/kde4/plugins/imageformats/kimg_ras.so
b1c1a000-b1c1b000 rw-p 00005000 08:05 1196117 /usr/lib/kde4/plugins/imageformats/kimg_ras.so
b1c1b000-b1c60000 r-xp 00000000 08:05 1179542 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2
b1c60000-b1c61000 r--p 00044000 08:05 1179542 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2
b1c61000-b1c62000 rw-p 00045000 08:05 1179542 /usr/lib/i386-linux-gnu/libjpeg.so.8.0.2
b1c62000-b1c72000 rw-p 00000000 00:00 0
b1c72000-b1cbd000 r-xp 00000000 08:05 1179456 /usr/lib/i386-linux-gnu/libjasper.so.1.0.0
b1cbd000-b1cbe000 r--p 0004a000 08:05 1179456 /usr/lib/i386-linux-gnu/libjasper.so.1.0.0
b1cbe000-b1cc1000 rw-p 0004b000 08:05 1179456 /usr/lib/i386-linux-gnu/libjasper.so.1.0.0
b1cc1000-b1cc7000 rw-p 00000000 00:00 0
b1cc7000-b1d09000 r-xp 00000000 08:05 1180900 /usr/lib/libHalf.so.6.0.0
b1d09000-b1d0a000 r--p 00041000 08:05 1180900 /usr/lib/libHalf.so.6.0.0
b1d0a000-b1d0b000 rw-p 00042000 08:05 1180900 /usr/lib/libHalf.so.6.0.0
b1d0b000-b1d21000 r-xp 00000000 08:05 1180893 /usr/lib/libIex.so.6.0.0
b1d21000-b1d22000 ---p 00016000 08:05 1180893 /usr/lib/libIex.so.6.0.0
b1d22000-b1d24000 r--p 00016000 08:05 1180893 /usr/lib/libIex.so.6.0.0
b1d24000-b1d25000 rw-p 00018000 08:05 1180893 /usr/lib/libIex.so.6.0.0
b1d25000-b1dd5000 r-xp 00000000 08:05 1181010 /usr/lib/libIlmImf.so.6.0.0
b1dd5000-b1dd7000 r--p 000af000 08:05 1181010 /usr/lib/libIlmImf.so.6.0.0
b1dd7000-b1dd8000 rw-p 000b1000 08:05 1181010 /usr/lib/libIlmImf.so.6.0.0
b1ddd000-b1de1000 r-xp 00000000 08:05 1196123 /usr/lib/kde4/plugins/imageformats/kimg_psd.so
b1de1000-b1de2000 r--p 00003000 08:05 1196123 /usr/lib/kde4/plugins/imageformats/kimg_psd.so
b1de2000-b1de3000 rw-p 00004000 08:05 1196123 /usr/lib/kde4/plugins/imageformats/kimg_psd.so
b1de3000-b1de8000 r-xp 00000000 08:05 1196118 /usr/lib/kde4/plugins/imageformats/kimg_pic.so
b1de8000-b1de9000 r--p 00004000 08:05 1196118 /usr/lib/kde4/plugins/imageformats/kimg_pic.so
b1de9000-b1dea000 rw-p 00005000 08:05 1196118 /usr/lib/kde4/plugins/imageformats/kimg_pic.so
b1dea000-b1df1000 r-xp 00000000 08:05 1196114 /usr/lib/kde4/plugins/imageformats/kimg_pcx.so
b1df1000-b1df2000 r--p 00007000 08:05 1196114 /usr/lib/kde4/plugins/imageformats/kimg_pcx.so
b1df2000-b1df3000 rw-p 00008000 08:05 1196114 /usr/lib/kde4/plugins/imageformats/kimg_pcx.so
b1df3000-b1e31000 r-xp 00000000 08:05 1182318 /usr/lib/i386-linux-gnu/libQtXml.so.4.8.3
b1e31000-b1e32000 r--p 0003e000 08:05 1182318 /usr/lib/i386-linux-gnu/libQtXml.so.4.8.3
b1e32000-b1e33000 rw-p 0003f000 08:05 1182318 /usr/lib/i386-linux-gnu/libQtXml.so.4.8.3
b1e33000-b1e36000 r-xp 00000000 08:05 1184738 /usr/lib/libdlrestrictions.so.1.0.0
b1e36000-b1e37000 r--p 00002000 08:05 1184738 /usr/lib/libdlrestrictions.so.1.0.0
b1e37000-b1e38000 rw-p 00003000 08:05 1184738 /usr/lib/libdlrestrictions.so.1.0.0
b1e38000-b1e47000 r-xp 00000000 08:05 655153 /lib/i386-linux-gnu/libbz2.so.1.0.4
b1e47000-b1e48000 r--p 0000e000 08:05 655153 /lib/i386-linux-gnu/libbz2.so.1.0.4
b1e48000-b1e49000 rw-p 0000f000 08:05 655153 /lib/i386-linux-gnu/libbz2.so.1.0.4
b1e49000-b1ec5000 r-xp 00000000 08:05 1182116 /usr/lib/i386-linux-gnu/libQtDBus.so.4.8.3
b1ec5000-b1ec6000 ---p 0007c000 08:05 1182116 /usr/lib/i386-linux-gnu/libQtDBus.so.4.8.3zsh: abort (core dumped) ./bitcoin-qt
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: hazek on January 01, 2013, 06:52:44 PM
I'm still testing this and I discovered that after running the client for between 24h -72h (I don't know when exactly) it closes on it's own without giving me any errors or anything. If I run it again it runs just fine. I should probably also mention that I don't really use this client, all I did was let it run under system tray and that this isn't the first time this happened. debug.log https://docs.google.com/open?id=0B6bqlVfJOOWsSi1zODN2Z1JWWTg log.0000000001 https://docs.google.com/open?id=0B6bqlVfJOOWsWUFsQmg4S0VOdjQ From event viewer: Log Name: Application
Source: Application Error
Date: 1.1.2013 18:06:07
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: hazek
Description:
Faulting application name: bitcoin-qt.exe, version: 0.7.99.0, time stamp: 0x4d44aa00
Faulting module name: bitcoin-qt.exe, version: 0.7.99.0, time stamp: 0x4d44aa00
Exception code: 0xc0000005
Fault offset: 0x0023c602
Faulting process id: 0x22e4
Faulting application start time: 0x01cde67fbfed7a10
Faulting application path: C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe
Faulting module path: C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe
Report Id: 87ca3637-5435-11e2-8c5a-685d43ee690b
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Level>2</Level>
<Task>100</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2013-01-01T17:06:07.000000000Z" />
<EventRecordID>5608</EventRecordID>
<Channel>Application</Channel>
<Computer>hazek</Computer>
<Security />
</System>
<EventData>
<Data>bitcoin-qt.exe</Data>
<Data>0.7.99.0</Data>
<Data>4d44aa00</Data>
<Data>bitcoin-qt.exe</Data>
<Data>0.7.99.0</Data>
<Data>4d44aa00</Data>
<Data>c0000005</Data>
<Data>0023c602</Data>
<Data>22e4</Data>
<Data>01cde67fbfed7a10</Data>
<Data>C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe</Data>
<Data>C:\Program Files (x86)\Bitcoin\bitcoin-qt.exe</Data>
<Data>87ca3637-5435-11e2-8c5a-685d43ee690b</Data>
</EventData>
</Event>
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on January 02, 2013, 03:10:57 AM
I guess this build is getting stale by now, so maybe I should make an updated next-test sometime soon.
I've had enough problems with the latest master code that I went back to the 2012-09 next-test myself...
Title: Re: Please test (if you dare): next-test 2012-11-25
Post by: Luke-Jr on April 12, 2013, 07:43:53 PM
Superceded with next-test 2013-04-12 (https://bitcointalk.org/?topic=175026)
|