[ANN] The first Armory-for-OSX Release! (Testing) - page 2.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Quote from: maxmint on April 18, 2013, 12:59:41 AM

I just tried it and unfortunately it never finnishes the inital scanning process (I left it open for 4 hours).
I'm on a brand new iMac with SSD, so I guess it should be done by now.

I'm running bitcoin-qt version 0.7.2 because I already had database problems when using 0.8.1 and had to do a rescan.
Could that be related to the armory problem?

Anyway, thanks so much for getting this started for OS X, really looking forward to a working version!

Can you send me a log file? And to clarify, it finishes "synchronizing" (the first one), but doesn't finish scanning the blockchain (the second one)? Are you using a non-standard datadir? I ask because I just found a bug that will be fixed when I release 0.88 soon.

0.7.1 should work. But I'll wait to say any more until I see a log file (etotheipi gmail com)

It sounds like 0.88 has to come with a caveat ... flip a coin ... if it's heads, it won't work on your OSX machine... gah!

maxmint

hero member

Activity: 700

Merit: 500

I just tried it and unfortunately it never finnishes the inital scanning process (I left it open for 4 hours).
I'm on a brand new iMac with SSD, so I guess it should be done by now.

I'm running bitcoin-qt version 0.7.2 because I already had database problems when using 0.8.1 and had to do a rescan.
Could that be related to the armory problem?

Anyway, thanks so much for getting this started for OS X, really looking forward to a working version!

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

The sip.so library has the same SHA1, so it has not changed. I would think that a timestamp or something would change when compiling, so perhaps it has not worked. It should be enough to do "brew uninstall sip" before and "brew install --env=std sip" afterwards. On the other hand, now that it looks like it is sip and not pyqt that is the culprit, I am less sure about the --env=std stuff.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Do you have a way to check whether anything really changed? I mean, I tried uninstalling everything, but there's a chance that it didn't do it right. I was thinking of restoring a fresh OSX install to try it, but I forgot to save the fresh-install state. I figured what I did was enough...

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

Quote from: etotheipi on April 17, 2013, 11:28:50 AM

Unfortunately, I don't have a system to test on that doesn't work, so the best I can do is try your suggestion, and post the results.

I uninstalled all the brew dependencies, cleaned all the build directories, added --env=std, and then rebuilt everything. For some reason, the result is 300 kB smaller... not sure why. But I did it, so you can try it. I have updated the original post here.

Dammit! No difference, it still crashes.

Well, if you can't fix the problem, document it

Some people (probably on older Macs) will find the app crashing - and will have to build it themselves. Certainly not an optimal solution, but the majority that don't see the problem will probably be happy anyway.

By the way, it is sip.so that cause the crash, according to Apple's crash reporter. I really cannot see why.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Unfortunately, I don't have a system to test on that doesn't work, so the best I can do is try your suggestion, and post the results.

I uninstalled all the brew dependencies, cleaned all the build directories, added --env=std, and then rebuilt everything. For some reason, the result is 300 kB smaller... not sure why. But I did it, so you can try it. I have updated the original post here.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

@etotheipi:

Could you try adding --env=std to the brew line installing sip and pyqt, it looks like the "superenv" feature in Homebrew is removing options specifying a more general architecture from the compilation commands. You will have to uninstall pyqt and sip, otherwise the script will not reinstall them.

something like

Code:

brew install --env=std cryptopp swig qt pyqt wget

(I have tested that sip and pyqt builds with that option, but I have not tested the rest. I suspect that it is pyqt that is causing the trouble.)

This is a long shot, but it might work. I could then test the resulting .app and see if it runs.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

I think I am on to something, and have a working hypothesis.

My evidence so far:

My .profile cause the app to work when called from the Terminal, disabling my .profile cause it to crash.
My .profile cause three libraries to be loaded from /usr/local instead of from etotheipi's app: sip.so, QtCore.so, QtGui.so
The crash is caused by an illegal instruction.
My MacBook is almost three years old.

I suspect that the problems are caused by one or more of the dependencies (sip or Qt) to be built with optimizations for the actual CPU on which it is built. Older CPUs will then not support one or more instructions in the code. This explains why only some people see the problem (those with older machines) and why it does not depend on the OS version.

To do: find the offending dependency, and fix its Makefile.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

I have made a tiny bit of progress. It turns out that on my machine, some libraries are loaded from /usr/local/Cellar which will not be present in normal installations.

I set the environment variable DYLD_PRINT_LIBRARIES to 1, that causes the dynamic loader to print the path of all libraries loaded to stderr, and then I started Armory from a terminal (that, by the way, prevents the crash, and fonts are slightly different, so something must be subtly different). In any case, a long list of libraries appears, and at the end these suspicious lines:

Code:

dyld: loaded: /usr/local/Cellar/qt/4.8.4/plugins/imageformats/libqgif.dylib
dyld: loaded: /usr/local/Cellar/qt/4.8.4/plugins/imageformats/libqico.dylib
dyld: loaded: /usr/local/Cellar/qt/4.8.4/plugins/imageformats/libqjpeg.dylib
dyld: loaded: /usr/local/Cellar/qt/4.8.4/plugins/imageformats/libqmng.dylib
dyld: loaded: /usr/local/Cellar/qt/4.8.4/plugins/imageformats/libqsvg.dylib
dyld: loaded: /usr/local/Cellar/qt/4.8.4/lib/QtSvg.framework/Versions/4/QtSvg
dyld: loaded: /usr/local/Cellar/qt/4.8.4/lib/QtXml.framework/Versions/4/QtXml
dyld: loaded: /usr/local/Cellar/qt/4.8.4/plugins/imageformats/libqtga.dylib
dyld: loaded: /usr/local/Cellar/qt/4.8.4/plugins/imageformats/libqtiff.dylib

These should certainly not be loaded from there! They don't appear to be included in the app. It could be some optional stuff that Qt loads if it finds it, explaining the strange crashes. Perhaps including them in the app would help.

EDIT: Removing .profile cause it to crash in the Terminal too. The self-build one still does not crash. This is the error message:

Code:

./MacOS/Armory: line 5: 925 Illegal instruction: 4 bin/python armorybuild/ArmoryQt.pyc

higuys

newbie

Activity: 28

Merit: 0

DYLD_LIBRARY_PATH tells the dynamic linker (dyld) to look in the specified places for libraries before it tries the locations in the binary headers and subsequently crashes because it can't find anything. It makes sense then that otool doesn't tell you where the libraries that are actually being used are coming from, as this is being done at runtime and requires no static changes to the binaries. You could set the correct places in the binaries, but you're going to have to edit the build configuration for qt and anything that uses those dependencies. Imo that's not going to change anything and you'll just spend time pulling your hair out.

I don't know what the problem is for everyone since there's only one post with actual error output and it's a segfault. I can't debug that without being able to reproduce it.

If it is trying to find more libraries installed globally that aren't there, you should get an error saying so. If this is the case it's not a big deal, and it can be fixed. I really don't think it is, though, as this would have come up again at some point in the past month.

I suspect some of the problems are coming from the fact that the minimum OS X version is set to 10.8 in the python executable, since etotheipi is building on 10.8.

You can do a search/replace with a hex editor on any binaries you think have a minimum version set like so:
Search: 24 00 00 00 10 00 00 00 00 08 0A 00 00 08 0A 00
Replace: 24 00 00 00 10 00 00 00 00 06 0A 00 00 06 0A 00

This will change the minimum version from 10.8 to 10.6

gwillen

newbie

Activity: 16

Merit: 0

So, in theory DYLD_LIBRARY_PATH isn't the right way to accomplish this sort of thing -- you're supposed to be able to embed library paths in the executable so that it knows where to look to load the right ones.

In practice I don't know how to do this, or what I'm talking about.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

Hmm, it does not look like otool respects the DYLD_LIBRARY_PATH variable that the driver script uses to cause loading from within the app bundle. I will look more at this tomorrow, I guess reading my previous post makes it pretty obvious that I am too tired for this

gwillen

newbie

Activity: 16

Merit: 0

So I will note also that if you 'otool -l' the .Python in the app, which appears to be the python library, you get (among other things):

Load command 8
cmd LC_VERSION_MIN_MACOSX
cmdsize 16
version 10.8
sdk 10.8

So that makes me suspect this might be the reason it crashes on less than 10.8? But I'm not sure why that would produce a segfault, so there may be multiple issues.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

OK, here is the list of which shared objects the shared objects in the app depend on, discovered with

Code:

otool -L `find . -name '*.so'`

(and similar for *.dylib). Here is the result, ~~it looks mostly harmless~~ EDIT: It looks like a lot of Qt stuff is loaded from /usr/local instead of from the App itself. So if we do not have the same Qt, it will probably break - but it looks like we do have the same, strange.

Code:

./MacOS/armorybuild/_CppBlockUtils.so:
	../_CppBlockUtils.so (compatibility version 0.0.0, current version 0.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
	/System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.2)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
./MacOS/lib/python2.7/site-packages/_psutil_osx.so:
	/System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, current version 744.12.0)
	/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/_psutil_posix.so:
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/phonon.so:
	/usr/local/lib/phonon.framework/Versions/4/phonon (compatibility version 4.4.0, current version 4.4.0)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/Qt.so:
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtCore.so:
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtDeclarative.so:
	/usr/local/lib/QtDeclarative.framework/Versions/4/QtDeclarative (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtScript.framework/Versions/4/QtScript (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtSvg.framework/Versions/4/QtSvg (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtSql.framework/Versions/4/QtSql (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtXmlPatterns.framework/Versions/4/QtXmlPatterns (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtNetwork.framework/Versions/4/QtNetwork (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtDesigner.so:
	/usr/local/lib/QtDesigner.framework/Versions/4/QtDesigner (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtScript.framework/Versions/4/QtScript (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtXml.framework/Versions/4/QtXml (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtGui.so:
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtHelp.so:
	/usr/local/lib/QtHelp.framework/Versions/4/QtHelp (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtSql.framework/Versions/4/QtSql (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtNetwork.framework/Versions/4/QtNetwork (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtMultimedia.so:
	/usr/local/lib/QtMultimedia.framework/Versions/4/QtMultimedia (compatibility version 4.8.0, current version 4.8.4)
	/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 45.0.0)
	/System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox (compatibility version 1.0.0, current version 1.0.0)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtNetwork.so:
	/usr/local/lib/QtNetwork.framework/Versions/4/QtNetwork (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtOpenGL.so:
	/usr/local/lib/QtOpenGL.framework/Versions/4/QtOpenGL (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL (compatibility version 1.0.0, current version 1.0.0)
	/System/Library/Frameworks/AGL.framework/Versions/A/AGL (compatibility version 1.0.0, current version 1.0.0)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtScript.so:
	/usr/local/lib/QtScript.framework/Versions/4/QtScript (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtScriptTools.so:
	/usr/local/lib/QtScriptTools.framework/Versions/4/QtScriptTools (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtScript.framework/Versions/4/QtScript (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtSql.so:
	/usr/local/lib/QtSql.framework/Versions/4/QtSql (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtSvg.so:
	/usr/local/lib/QtSvg.framework/Versions/4/QtSvg (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtTest.so:
	/usr/local/lib/QtTest.framework/Versions/4/QtTest (compatibility version 4.8.0, current version 4.8.4)
	/System/Library/Frameworks/IOKit.framework/Versions/A/IOKit (compatibility version 1.0.0, current version 275.0.0)
	/System/Library/Frameworks/Security.framework/Versions/A/Security (compatibility version 1.0.0, current version 55179.1.0)
	/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 45.0.0)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtWebKit.so:
	/usr/local/lib/QtWebKit.framework/Versions/4/QtWebKit (compatibility version 4.9.0, current version 4.9.3)
	/usr/local/lib/QtGui.framework/Versions/4/QtGui (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtNetwork.framework/Versions/4/QtNetwork (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtXml.so:
	/usr/local/lib/QtXml.framework/Versions/4/QtXml (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/PyQt4/QtXmlPatterns.so:
	/usr/local/lib/QtXmlPatterns.framework/Versions/4/QtXmlPatterns (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtNetwork.framework/Versions/4/QtNetwork (compatibility version 4.8.0, current version 4.8.4)
	/usr/local/lib/QtCore.framework/Versions/4/QtCore (compatibility version 4.8.0, current version 4.8.4)
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/sip.so:
	/usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, current version 56.0.0)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/twisted/python/sendmsg.so:
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/twisted/runner/portmap.so:
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/twisted/test/raiser.so:
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/lib/python2.7/site-packages/zope/interface/_zope_interface_coptimizations.so:
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)


./Dependencies/libpng15.15.dylib:
	/usr/local/lib/libpng15.15.dylib (compatibility version 30.0.0, current version 30.0.0)
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)
./MacOS/armorybuild/Armory.app/Contents/Dependencies/libpng15.15.dylib:
	/usr/local/lib/libpng15.15.dylib (compatibility version 30.0.0, current version 30.0.0)
	/usr/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.5)
	/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 169.3.0)

I did the same with the self-built version. There were two differences, the version number of /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation that psutils expect (version 744.12.0 in your app, 744.18.0 in the version that I built myself.) And the app you built contains both ./Dependencies/libpng15.15.dylib and ./MacOS/armorybuild/Armory.app/Contents/Dependencies/libpng15.15.dylib whereas the one I built only contains the former.

I have really no idea what this means - I will investigate

EDIT: Dependency on /usr/local/lib/QtGui.framework/Versions/4/QtGui and one more looks bad, bad, bad!

EDIT 2: Everything in this post is dubious, since the correct environment for loading dynamic libraries was not set. I will try again after getting some coffee

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

Yes, I think we can, with otool -L. I will give it a try, and whether successful or not I will report back here.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Maybe someone with more lower-level tracing experience than me can help out: can we trace the dependencies used by the .app I created? It's supposed to be completely self-contained, but it sounds like there's still some system libraries being accessed, some of which are not compatible with the ones in my VM.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

OK, if I build the app myself, it works.
If I download the app you built to my laptop, it crashes.
If I download it to my wife's macbook, it works just fine. It can even print paper backups! (which has not worked on my laptop since multithreading appeared)

I guess it has something to do with conflicting versions of something that I have installed - I have installed all kinds of junk on this machine for some time now. I will investigate further tonight or tomorrow, have to run now.

etotheipi

legendary

Activity: 1428

Merit: 1093

Core Armory Developer

Quote from: picobit on April 16, 2013, 09:35:30 AM

I checked the Mac app on my Mountain Lion 10.8.3 MacBook Pro.

Unfortunately, it is highly unstable. The app crashes almost no matter what I try to do. For example, I have a testing wallet with no encryption. Clicking on Make Paper Backup cause a crash, also if bitcoin-qt is not running.

I tried to build from source, that version works, but it is clearly a different version. The app is 0.87.98, the one I build from source is 0.87.3. Probably I am building from the wrong branch, which branch should I build to test this? I was planning to test if it is the build or the armory version that is unstable by building myself (all previous versions that I have built from source have been rock stable). If it is the app only, I could also modify the makefile to build with debugging enabled, and attach a debugger (although debugging a multhithreaded program is new for me).

In any case I am busy at work, so my progress may be slow.

Ack. Not good! It seems to be random, when it works and when it doesn't (not by OSX version).

If you want to do further testing, use the "testing" branch. Only the blockdata access stuff is multi-threaded...everything else runs in a single thread. I don't think it should be too bad.

picobit

hero member

Activity: 547

Merit: 500

Decor in numeris

I checked the Mac app on my Mountain Lion 10.8.3 MacBook Pro.

Unfortunately, it is highly unstable. The app crashes almost no matter what I try to do. For example, I have a testing wallet with no encryption. Clicking on Make Paper Backup cause a crash, also if bitcoin-qt is not running.

I tried to build from source, that version works, but it is clearly a different version. The app is 0.87.98, the one I build from source is 0.87.3. Probably I am building from the wrong branch, which branch should I build to test this? I was planning to test if it is the build or the armory version that is unstable by building myself (all previous versions that I have built from source have been rock stable). If it is the app only, I could also modify the makefile to build with debugging enabled, and attach a debugger (although debugging a multhithreaded program is new for me).

In any case I am busy at work, so my progress may be slow.

camolist

hero member

Activity: 896

Merit: 1000

lots of testing today on both mac (online) and ubuntu (offline)

mac is the release from this this thread on 10.7.5 osx
ubuntu is on 10.04 using 0.86.3-beta dependencies bundle

backups importing and exporting cd/usb copies
recovering from paper wallets

sending online/offline transactions

all checks out as far as i can tell

Topic: [ANN] The first Armory-for-OSX Release! (Testing) - page 2. (Read 4627 times)