Upgrading from 3.2 gives Segmentation fault

[rupy]

So what do I have to delete in .bitcoin to get the latest release to work?

[jgarzik]

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.

[rupy]

Ok, i renamed the .bitcoin folder and still Segmentation fault... and the folder is empty, no logs, no nothing! I run suse 11.3...

[jgarzik]

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?

[notme]

Version 3.2 of what?

The latest version  of the official client is 0.7.2.

[rupy]

No debug at all.

I was using bitcoin 3.2 which worked fine but lately it spins out of control and wears my SSD...

[Pieter Wuille]

Do you mean 0.3.20?

[rupy]

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...

[notme]

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

[rupy]

Ok, compilation fails: http://pastebin.com/iVpPwnzQ

[notme]

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.

[rupy]

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?

[notme]

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.

[rupy]

gdb gives:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6d476b2 in QMetaObject::cast(QObject*) const ()
   from /usr/lib64/libQtCore.so.4

will try berkeley 4.8

[rupy]

Hm, can someone help me get the build up?

Which file do I have to download in order to get berkeley files to be reachable for the bitcoin build?

[deepceleron]

Would it help to upgrade to a distro only two years old?
http://www.howtoforge.com/how-to-upgrade-opensuse-11.3-to-11.4-desktop-and-server

[rupy]

Well, the machine I use is a 24/7 server and my main work development machine so I can't risk anything going haywire... I know that updating versions like that always breaks important things...

[deepceleron]

gdb gives:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff6d476b2 in QMetaObject::cast(QObject*) const ()
   from /usr/lib64/libQtCore.so.4

will try berkeley 4.8

Bitcoin 0.3.xx does not use the Qt library, it uses wxwidgets.

Bitcoin targets QT version 4.8.2 with compatibility for V5. It looks like OpenSUSE 11.3 shipped with QT v4.6.0 If you have a Gnome desktop, Qt may not even be installed.

Install/Updates for Qt - no listing for 11.3, the page starts at 11.4 (and the download site only has 12.1+)
http://en.opensuse.org/KDE_repositories#Qt

[rupy]

See this is one problem with linux (the other being that distributions make their own tools that should be standardized; yum, apt-get, yast... etc), it's a big mess to update after service life ends and even before because of spaghetti dependencies on shit that never works as expected if you touch one straw... So my solution as a software developer is to upgrade versions of dependencies ONLY when it's really really necessary.

So basically latest bitcoin is useless to me here...

I actually have SuSE 11.2, so which version of bitcoin uses QT 4.5.3 or older?

[notme]

See this is one problem with linux (the other being that distributions make their own tools that should be standardized; yum, apt-get, yast... etc), it's a big mess to update after service life ends and even before because of spaghetti dependencies on shit that never works as expected if you touch one straw... So my solution as a software developer is to upgrade versions of dependencies ONLY when it's really really necessary.

So basically latest bitcoin is useless to me here...

I actually have SuSE 11.2, so which version of bitcoin uses QT 4.5.3 or older?

Keeping your software up to date not only makes your life much easier, it makes your data much safer.  I would sign transactions by hand before I used a distro that old to hold a bitcoin wallet.  There are way too many known exploits for the code you are running.

Rolling releases and constant updates FTW.  I love Arch .