Pages:
Author

Topic: Upgrading from 3.2 gives Segmentation fault - page 2. (Read 3379 times)

legendary
Activity: 1904
Merit: 1002
There is no configure file!

But ok, I resolved the boost dependency... but now it can't compile the db because suse 11.3 has berkeley 4.5 and bitcoin requires 4.8, so thats the segmentation fault right there I guess?

So is it possible to fix this?

If you're using a direct git clone rather than a release tarball, you need to run ./autogen.sh first to generate ./configure, same as nearly every other autotools setup in existence.

Yes, you can compile and install berkeley 4.8 yourself if your distro doesn't provide a package.

If you run bitcoin in a gdb session you should be able to get a backtrace that tells you where the segfault is occurring.  I believe the binaries from bitcoin.org have all the dependencies compiled in, so I don't think the berkeley db version is your issue.
hero member
Activity: 725
Merit: 503
There is no configure file!

But ok, I resolved the boost dependency... but now it can't compile the db because suse 11.3 has berkeley 4.5 and bitcoin requires 4.8, so thats the segmentation fault right there I guess?

So is it possible to fix this?
legendary
Activity: 1904
Merit: 1002
Ok, compilation fails: http://pastebin.com/iVpPwnzQ

Looks like you are missing the libboost development package.  Make sure configure is happy before you try to run make.
hero member
Activity: 725
Merit: 503
Ok, compilation fails: http://pastebin.com/iVpPwnzQ
legendary
Activity: 1904
Merit: 1002
January 09, 2013, 04:07:20 AM
#9
Ah, yes. But thats not the issue the issue is that since 0.6.xxxx > the client segmentation faults on suse 11.3, works fine on my suse 12...

likely a library version issue... just compile from git
hero member
Activity: 725
Merit: 503
January 09, 2013, 04:05:28 AM
#8
Ah, yes. But thats not the issue the issue is that since 0.6.xxxx > the client segmentation faults on suse 11.3, works fine on my suse 12...
legendary
Activity: 1072
Merit: 1181
January 08, 2013, 03:24:40 PM
#7
Do you mean 0.3.20?
hero member
Activity: 725
Merit: 503
January 08, 2013, 12:44:29 PM
#6
No debug at all.

I was using bitcoin 3.2 which worked fine but lately it spins out of control and wears my SSD...
legendary
Activity: 1904
Merit: 1002
January 07, 2013, 08:36:49 PM
#5
Version 3.2 of what?

The latest version  of the official client is 0.7.2.
legendary
Activity: 1596
Merit: 1100
January 07, 2013, 11:28:38 AM
#4
Ok, i renamed the .bitcoin folder and still Segmentation fault... and the folder is empty, no logs, no nothing! I run suse 11.3...

Can you post the exact errors you get?  No debug.log appears at all?

hero member
Activity: 725
Merit: 503
January 07, 2013, 06:38:48 AM
#3
Ok, i renamed the .bitcoin folder and still Segmentation fault... and the folder is empty, no logs, no nothing! I run suse 11.3...
legendary
Activity: 1596
Merit: 1100
January 03, 2013, 04:21:25 PM
#2
So what do I have to delete in .bitcoin to get the latest release to work?

Technically you can delete everything except wallet.dat and bitcoin.conf.

hero member
Activity: 725
Merit: 503
January 03, 2013, 03:53:32 PM
#1
So what do I have to delete in .bitcoin to get the latest release to work?
Pages:
Jump to: