Segmentation Fault at block 225500 while dumping the blockchain about blockparser HOT 9 CLOSED

Try running

dmesg

afterwards and see if you ran out of memory

from blockparser.

dmesg tells me the following:

[ 8865.765301] parser[27351]: segfault at 10 ip 000000000046556a sp 00007fff38d00790 error 6 in parser[400000+96000]

i wasn't able to find out what "error 6" means.
my machine has 8gb of ram, would you say this is insufficient to dump the chain?

from blockparser.

Not sure. Runs fine for me with 8 gigs, but it does take awhile. It's possible you are running out of swap memory and need more. Try running

watch -d free -m

While you run the command and see what you get. This will show your ram allocation in real time in MBs. Do the other commands run fine for you?

./parser stats
./parser allBalances -a 100
./parser allBalances -a 230000

You could also try downloading valgrind http://www.valgrind.org/downloads/current.html to get some more info on what's going on.

valgrind ./parser sqldump

from blockparser.

I'm having what I guess is the same problem.

$ ./parser stats

info: starting command "simpleStats"
Segmentation fault

dmesg:

parser[4600]: segfault at 10 ip 0000000000450ae3 sp 00007fff0a547050 error 6 in parser[400000+92000]

from blockparser.

I had this issue recently and I found that updating bitcoind version and rebooting made it go away. apt-get install bitcoind on ubuntu. You can also try running some bitcoind commands to see if it's working properly. bitcoind getinfo

from blockparser.

[3027241.587691] parser[25537]: segfault at 0 ip 00000000004054b7 sp 00007fffb529b520 error 4 in parser[400000+79000]
What is the meaning of error 4?

I am running it on 4gb RAM machine

$ valgrind ./parser simpleStats
==26897== Memcheck, a memory error detector
==26897== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==26897== Using Valgrind-3.10.0.SVN and LibVEX; rerun with -h for copyright info
==26897== Command: ./parser simpleStats
==26897==

info: starting command "simpleStats"
==26897== Invalid read of size 8
==26897== at 0x4054B7: ??? (in /root/blockparser/parser)
==26897== by 0x574CEC4: (below main) (libc-start.c:287)
==26897== Address 0x0 is not stack'd, malloc'd or (recently) free'd
==26897==
==26897==
==26897== Process terminating with default action of signal 11 (SIGSEGV)
==26897== Access not within mapped region at address 0x0
==26897== at 0x4054B7: ??? (in /root/blockparser/parser)
==26897== by 0x574CEC4: (below main) (libc-start.c:287)
==26897== If you believe this happened as a result of a stack
==26897== overflow in your program's main thread (unlikely but
==26897== possible), you can try to increase the size of the
==26897== main thread stack using the --main-stacksize= flag.
==26897== The main thread stack size used in this run was 8388608.
==26897==
==26897== HEAP SUMMARY:
==26897== in use at exit: 531,468 bytes in 111 blocks
==26897== total heap usage: 241 allocs, 130 frees, 539,361 bytes allocated
==26897==
==26897== LEAK SUMMARY:
==26897== definitely lost: 0 bytes in 0 blocks
==26897== indirectly lost: 0 bytes in 0 blocks
==26897== possibly lost: 2,865 bytes in 64 blocks
==26897== still reachable: 528,603 bytes in 47 blocks
==26897== suppressed: 0 bytes in 0 blocks
==26897== Rerun with --leak-check=full to see details of leaked memory
==26897==
==26897== For counts of detected and suppressed errors, rerun with: -v
==26897== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
Segmentation fault (core dumped)

from blockparser.

Try to see if latest still has this problem.
Given that blockparser does not use mmap anymore, this is likely going to be fixed.
Also blockparser i snow much faster.

from blockparser.

[71549.799128] show_signal_msg: 15 callbacks suppressed
[71549.799131] parser[1894]: segfault at 7ff1bede7414 ip 0000000000430d22 sp 00007ffdcdc12170 error 4 in parser[400000+47000]

from blockparser.

I've got a 15GB machine and it shows 90% of RAM goes to the parser and it will be running for many hours, hope the memory will not increase any further but I can see why my 8GB machine also segfaults

from blockparser.