Bitcoin Forum
December 08, 2016, 08:11:07 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 [229] 230 231 232 »
  Print  
Author Topic: Armory - Discussion Thread  (Read 482123 times)
TimS
Sr. Member
****
Offline Offline

Activity: 247


View Profile WWW
July 13, 2015, 01:43:49 PM
 #4561

nope. if you'd like to sweep coins from a privkey, your fsck'd.
As I understand it, a pruned node still has the UTXO set (this is the database of unspent transactions, keyed by txid, that is necessary for knowing if tx's that come across the client are valid and should be relayed or not). Assuming Armory is written to support it (not yet, I'm sure, but it could be), you can still sweep/import a private key, and receive and spend bitcoins. The biggest difference is that you won't be able to know the history of old, already-spent transactions. Also, this might be an issue as Armory may have a harder time figuring out how many addresses to generate from your wallet, if it doesn't know that the first e.g. 150 addresses are already used and spent from.
1481184667
Hero Member
*
Offline Offline

Posts: 1481184667

View Profile Personal Message (Offline)

Ignore
1481184667
Reply with quote  #2

1481184667
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481184667
Hero Member
*
Offline Offline

Posts: 1481184667

View Profile Personal Message (Offline)

Ignore
1481184667
Reply with quote  #2

1481184667
Report to moderator
1481184667
Hero Member
*
Offline Offline

Posts: 1481184667

View Profile Personal Message (Offline)

Ignore
1481184667
Reply with quote  #2

1481184667
Report to moderator
goatpig
Moderator
Legendary
*
Offline Offline

Activity: 1330

Armory Developer


View Profile
July 13, 2015, 01:59:12 PM
 #4562

There are ways to make pruned Core nodes work with Armory but that's not an item on the list at the moment, so no point speculating.

btcarmory.com
visdude
Hero Member
*****
Offline Offline

Activity: 670


View Profile
July 19, 2015, 07:01:20 AM
 #4563

Okay I am a newbie when it comes to armory.

 I have a pc with an intel 4570t cpu

2 sticks of 8gb ram

a 250 gb samsung ssd


it is a new build from old parts.

it has windows 7 ultimate 64 not 32

So what armory is best to load to this.

92 ?

and where is the link? on the site below


https://bitcoinarmory.com/


so I have been looking at the site a bit.  and I want the windows 7 pc mentioned above to be the offline pc.

I can use a second windows 7 pc as a partner online pc….  it has windows 7 home  as the os.  I also have a mac mini with 10.10.3 os  could this works as the online pc with the windows 7 offline pc?

It's overkill, Phil Grin.  A netbook is perfect for an offline Armory; small, very portable and easy to hide.
visdude
Hero Member
*****
Offline Offline

Activity: 670


View Profile
July 19, 2015, 07:08:41 AM
 #4564


I tried to update my offline Armory 0.92.3 with "armory_0.93.2_winAll.exe" (32- and 64-bit) but Bitcoin Armory Setup is telling me "You cannot install this version on a 32-bit sytem". Why?
Carlton Banks
Legendary
*
Offline Offline

Activity: 1470



View Profile
July 19, 2015, 08:34:04 AM
 #4565


I tried to update my offline Armory 0.92.3 with "armory_0.93.2_winAll.exe" (32- and 64-bit) but Bitcoin Armory Setup is telling me "You cannot install this version on a 32-bit sytem". Why?


Software function libraries. 93.x relies on different software libraries to versions <= 92.3, and those new libraries cannot operate with 32-bit CPU's for technical reasons. Goatpig has previously mentioned that version 0.94 could have 32-bit compatibility restored, and there's a bigger difference between the benefits of 0.94 and the benefits of 0.93 IMO (faster sync, smaller databases on disk etc).

Vires in numeris
visdude
Hero Member
*****
Offline Offline

Activity: 670


View Profile
July 19, 2015, 11:24:49 AM
 #4566


I tried to update my offline Armory 0.92.3 with "armory_0.93.2_winAll.exe" (32- and 64-bit) but Bitcoin Armory Setup is telling me "You cannot install this version on a 32-bit sytem". Why?


Software function libraries. 93.x relies on different software libraries to versions <= 92.3, and those new libraries cannot operate with 32-bit CPU's for technical reasons. Goatpig has previously mentioned that version 0.94 could have 32-bit compatibility restored, and there's a bigger difference between the benefits of 0.94 and the benefits of 0.93 IMO (faster sync, smaller databases on disk etc).

Thank you.
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 28, 2015, 06:46:04 PM
 #4567

is 0.93.2 working with Core 0.11.0?
yslyung
Legendary
*
Offline Offline

Activity: 1064


Mine Mine Mine


View Profile
July 28, 2015, 07:55:03 PM
 #4568

is 0.93.2 working with Core 0.11.0?

Yes no problem at all.

i'm on win 7 64bit. all is working well including the offline wallet.

@philipma, if you need any help or questions with offline storage & armory stuff, you can pm me.
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 28, 2015, 08:19:50 PM
 #4569

is 0.93.2 working with Core 0.11.0?

Yes no problem at all.

i'm on win 7 64bit. all is working well including the offline wallet.

@philipma, if you need any help or questions with offline storage & armory stuff, you can pm me.

does it work in Ubuntu?
doug_armory
Sr. Member
****
Offline Offline

Activity: 255

Senior Developer - Armory


View Profile WWW
July 29, 2015, 03:07:46 AM
 #4570

Yes, although online Armory must be on a 64-bit system when using Ubuntu.

Senior Developer -  Armory Technologies, Inc.
cypherdoc
Legendary
*
Offline Offline

Activity: 1764



View Profile
July 30, 2015, 04:22:39 AM
 #4571

what can i do to get connections unstuck from zero?

Code:
"version" : 110000,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 366904,
    "timeoffset" : 0,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 51076366303.48192596,
    "testnet" : false,
    "keypoololdest" : 1407033834,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : "
"
marcus_of_augustus
Legendary
*
Offline Offline

Activity: 2100



View Profile
July 30, 2015, 07:45:13 AM
 #4572

what can i do to get connections unstuck from zero?

Code:
"version" : 110000,
    "protocolversion" : 70002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 366904,
    "timeoffset" : 0,
    "connections" : 0,
    "proxy" : "",
    "difficulty" : 51076366303.48192596,
    "testnet" : false,
    "keypoololdest" : 1407033834,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : "
"


Hire a wretchedly expensive consultant who knows what they are doing. Maybe someone who is knowledgeable about bitcoin and gets paid insane amounts of money for endorsing bleeding-edge cryptographic hashing equipment and algorithms.

Ente
Legendary
*
Offline Offline

Activity: 1834



View Profile
July 30, 2015, 03:27:08 PM
 #4573

Yes.

It goes something like this:
- anything fishy in your bitcoin.conf?
- is the port forwarded so external nodes can reach your bitcoind?
- any packetfilter/firewall/antivirus in between?

Check that with https://getaddr.bitnodes.io/, there's a test in the lower area.

Ente
koeppelmann
Newbie
*
Offline Offline

Activity: 6


View Profile
August 02, 2015, 05:49:08 AM
 #4574

My armory breaks down every time I start it. Or better: as soon as it is connected to BitcoinQT (while organziing blockchain). I have the latest version of BitcoinQT and Armory. It was everything ok for weeks. But today it happend EVERY time (I tired at least 10 times, reboot, ...) I have a mac.

Any hint what I should do? Rebuilt blockchain? Reinstall Armory?

Those are the first lines of the error report:

rocess:               Python [822]
Path:                  /Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               Huh
Code Type:             X86-64 (Native)
Parent Process:        Huh [1]
Responsible:           Python [822]
User ID:               501

Date/Time:             2015-08-01 22:47:16.836 -0700
OS Version:            Mac OS X 10.10.4 (14E46)
Report Version:        11
Anonymous UUID:        0342B016-FFD5-109B-1719-DF5FD2B7FFA6

Sleep/Wake UUID:       A3F7E20C-0AA7-44AD-8CD9-7D44B0AF6A3F

Time Awake Since Boot: 2400 seconds
Time Since Wake:       1300 seconds

Crashed Thread:        8

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       0x000000000000000a, 0x0000000ae461e001

VM Regions Near 0xae461e001:
    MALLOC_LARGE           0000000adde02000-0000000ade103000 [ 3076K] rw-/rwx SM=PRV 
--> mapped file            0000000ade103000-0000000ae64c9000 [131.8M] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
    MALLOC_LARGE           0000000ae64c9000-0000000ae67ca000 [ 3076K] rw-/rwx SM=PRV 

Thread 0:: Dispatch queue: com.apple.main-thread
0   libdispatch.dylib                0x00007fff8b59f7f8 _dispatch_queue_wakeup_with_qos_slow + 1075
1   com.apple.coreui                 0x00007fff8d155bed PerformBlockWithThemeRegistry + 102
2   com.apple.coreui                 0x00007fff8d155e7e _LookupThemeProvider + 232
3   com.apple.coreui                 0x00007fff8d1391e1 -[CUIThemeFacet _approximateRenditionForRenditionKey:] + 109
4   com.apple.coreui                 0x00007fff8d13e706 -[CUIThemeFacet imageSize] + 83
doug_armory
Sr. Member
****
Offline Offline

Activity: 255

Senior Developer - Armory


View Profile WWW
August 03, 2015, 02:14:28 AM
 #4575

My armory breaks down every time I start it. Or better: as soon as it is connected to BitcoinQT (while organziing blockchain). I have the latest version of BitcoinQT and Armory. It was everything ok for weeks. But today it happend EVERY time (I tired at least 10 times, reboot, ...) I have a mac.

Any hint what I should do? Rebuilt blockchain? Reinstall Armory?

I use Armory on my Mac often and very rarely see crashes. I've heard some people are still having performance issues. My theory is that Qt (an underlying library) just doesn't play nice with some Macs due to threading issues. I've been trying to make some noise and get this investigated. If anybody would like to help me out, please upvote this bug. The patch I posted there doesn't fix everything but it does fix a lot of issues. Maybe drawing more attention to it will lead to more long-term fixes.

*jumps off soapbox* Anyway, regarding this crash, if it happens again, look for the following bits of info.

Quote
Crashed Thread:        8

(...)

Thread 0:: Dispatch queue: com.apple.main-thread
0   libdispatch.dylib                0x00007fff8b59f7f8 _dispatch_queue_wakeup_with_qos_slow + 1075
1   com.apple.coreui                 0x00007fff8d155bed PerformBlockWithThemeRegistry + 102
2   com.apple.coreui                 0x00007fff8d155e7e _LookupThemeProvider + 232
3   com.apple.coreui                 0x00007fff8d1391e1 -[CUIThemeFacet _approximateRenditionForRenditionKey:] + 109
4   com.apple.coreui                 0x00007fff8d13e706 -[CUIThemeFacet imageSize] + 83

The crashed thread will test you which trace to post, which is the gobbledygook at the bottom of my quote. I'm guessing it'll be a Qt issue but I could be wrong.

Also, just curious, do you put your Mac to sleep often? I do get the odd crash on Yosemite after I've put my Mac to sleep something like 12-15 times, along with other odd behavior. Some of it might be Armory - I'm investigating right now - and some of it is almost certainly Qt (or Yosemite causing Qt to freak out).

Senior Developer -  Armory Technologies, Inc.
koeppelmann
Newbie
*
Offline Offline

Activity: 6


View Profile
August 11, 2015, 05:27:11 AM
 #4576

Thanks for the response. I build the Bitcoin BD again but I still have the problem. I can not use Armory at all - while starting it always crashes.

It seems that you are and the problem is related to QT:

Code:
Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        0x00007fff873074de mach_msg_trap + 10
1   libsystem_kernel.dylib        0x00007fff8730664f mach_msg + 55
2   com.apple.CoreFoundation      0x00007fff8f6b4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      0x00007fff8f6b437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      0x00007fff8f6b3bd8 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox            0x00007fff8df3d56f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox            0x00007fff8df3d2ea ReceiveNextEventCommon + 431
7   com.apple.HIToolbox            0x00007fff8df3d12b _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit              0x00007fff8a7578ab _DPSNextEvent + 978
9   com.apple.AppKit              0x00007fff8a756e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
10  com.apple.AppKit              0x00007fff8a74caf3 -[NSApplication run] + 594
11  QtGui                          0x00000001040d684a QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 538
12  QtCore                        0x000000010366aaad QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 477
13  QtCore                        0x000000010366dcc7 QCoreApplication::exec() + 199
14  QtGui.so                      0x00000001038d5a10 meth_QApplication_exec_(_object*, _object*) + 80
15  org.python.python              0x00000001000b07f6 PyEval_EvalFrameEx + 20486
16  org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
17  org.python.python              0x00000001000aaeb6 PyEval_EvalCode + 54
18  org.python.python              0x00000001000d43e4 PyRun_FileExFlags + 164
19  org.python.python              0x00000001000d3f61 PyRun_SimpleFileExFlags + 769
20  org.python.python              0x00000001000eafd7 Py_Main + 3063
21  Python                        0x0000000100000e55 0x100000000 + 3669
22  Python                        0x0000000100000d71 0x100000000 + 3441

Yes, I do use the sleep function often - basically always, I never shut my mac down. But i also started to restart it, start BitcoinQt, start Amory -> same problem.
doug_armory
Sr. Member
****
Offline Offline

Activity: 255

Senior Developer - Armory


View Profile WWW
August 12, 2015, 01:42:50 AM
 #4577

Hello. Is thread 0 the one that actually crashed? It could be a different one. The crash report will always say which one it is.

Senior Developer -  Armory Technologies, Inc.
Searinox
Member
**
Offline Offline

Activity: 100

Do you like fire? I'm full of it.


View Profile
August 16, 2015, 08:42:40 AM
 #4578

Armory Version 0.93.2
Bitcoind version 0.11.0 Running UNMANAGED by Armory
Builds: both x64
OS: Windows 7 x64 SP1 + all recent updates

Internet was down for a whole day and when it picked up again, bitcoind began quickly catching up with the network again, at first Armory ate the new blocks just fine but then it threw a "missing headers" error. When I restarted it rescanned the entire history, then there were no more issues.

The only thing I have in the log is this:

Code:
2015-08-16 11:16 (INFO) -- ArmoryQt.py:6249 - New Block! : 369959
2015-08-16 11:16 (INFO) -- ArmoryQt.py:6257 - Current block number: 369959
2015-08-16 11:16 (INFO) -- ArmoryQt.py:6249 - New Block! : 369960
2015-08-16 11:16 (INFO) -- ArmoryQt.py:6257 - Current block number: 369960
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1076 - C++ block utilities loaded successfully
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1186 -
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1187 -
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1188 -
2015-08-16 11:30 (INFO) -- ArmoryUtils.pyc:1189 -

11:16 is when it crashed, 11:30 is when I came back to the PC to notice the crash and restarted it.
koeppelmann
Newbie
*
Offline Offline

Activity: 6


View Profile
August 16, 2015, 08:21:30 PM
 #4579

Hello. Is thread 0 the one that actually crashed? It could be a different one. The crash report will always say which one it is.

It is thread 5:

Code:
Process:               Python [9657]
Path:                  /Applications/Armory.app/Contents/MacOS/Python
Identifier:            com.armory.armory
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Python [9657]
User ID:               501

Date/Time:             2015-08-16 13:19:16.916 -0700
OS Version:            Mac OS X 10.10.5 (14F27)
Report Version:        11
Anonymous UUID:        0342B016-FFD5-109B-1719-DF5FD2B7FFA6

Sleep/Wake UUID:       CBCA24F7-E0BC-4954-86F2-65CC9B033F86

Time Awake Since Boot: 86000 seconds
Time Since Wake:       10000 seconds

Crashed Thread:        5

Exception Type:        EXC_BAD_ACCESS (SIGBUS)
Exception Codes:       0x000000000000000a, 0x0000000ae33c8001

VM Regions Near 0xae33c8001:
    mapped file            000000011f02f000-0000000adcead000 [ 39.0G] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
--> mapped file            0000000adcead000-0000000ae5273000 [131.8M] r--/rwx SM=PRV  /Users/USER/Library/Application Support/Armory/*
    MALLOC_LARGE           0000000ae5273000-0000000ae52f3000 [  512K] rw-/rwx SM=PRV 

Thread 0:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        0x00007fff90b614de mach_msg_trap + 10
1   libsystem_kernel.dylib        0x00007fff90b6064f mach_msg + 55
2   com.apple.CoreFoundation      0x00007fff913d4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      0x00007fff913d437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      0x00007fff913d3bd8 CFRunLoopRunSpecific + 296
5   com.apple.HIToolbox            0x00007fff8fe2456f RunCurrentEventLoopInMode + 235
6   com.apple.HIToolbox            0x00007fff8fe242ea ReceiveNextEventCommon + 431
7   com.apple.HIToolbox            0x00007fff8fe2412b _BlockUntilNextEventMatchingListInModeWithFilter + 71
8   com.apple.AppKit              0x00007fff92b018ab _DPSNextEvent + 978
9   com.apple.AppKit              0x00007fff92b00e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 346
10  com.apple.AppKit              0x00007fff92af6af3 -[NSApplication run] + 594
11  QtGui                          0x00000001040d684a QEventDispatcherMac::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) + 538
12  QtCore                        0x000000010366aaad QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 477
13  QtCore                        0x000000010366dcc7 QCoreApplication::exec() + 199
14  QtGui.so                      0x00000001038d5a10 meth_QApplication_exec_(_object*, _object*) + 80
15  org.python.python              0x00000001000b07f6 PyEval_EvalFrameEx + 20486
16  org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
17  org.python.python              0x00000001000aaeb6 PyEval_EvalCode + 54
18  org.python.python              0x00000001000d43e4 PyRun_FileExFlags + 164
19  org.python.python              0x00000001000d3f61 PyRun_SimpleFileExFlags + 769
20  org.python.python              0x00000001000eafd7 Py_Main + 3063
21  Python                        0x0000000100000e55 0x100000000 + 3669
22  Python                        0x0000000100000d71 0x100000000 + 3441

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        0x00007fff90b67232 kevent64 + 10
1   libdispatch.dylib              0x00007fff94516a6a _dispatch_mgr_thread + 52

Thread 2:: com.apple.CFSocket.private
0   libsystem_kernel.dylib        0x00007fff90b663fa __select + 10
1   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
2   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
3   libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 3:
0   libsystem_kernel.dylib        0x00007fff90b614de mach_msg_trap + 10
1   libsystem_kernel.dylib        0x00007fff90b6064f mach_msg + 55
2   com.apple.CoreFoundation      0x00007fff913d4eb4 __CFRunLoopServiceMachPort + 212
3   com.apple.CoreFoundation      0x00007fff913d437b __CFRunLoopRun + 1371
4   com.apple.CoreFoundation      0x00007fff913d3bd8 CFRunLoopRunSpecific + 296
5   com.apple.AppKit              0x00007fff92bc956b _NSEventThread + 137
6   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
7   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
8   libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 4:
0   libsystem_kernel.dylib        0x00007fff90b663fa __select + 10
1   org.python.python              0x00000001000b07f6 PyEval_EvalFrameEx + 20486
2   org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
3   org.python.python              0x00000001000364dc function_call + 364
4   org.python.python              0x0000000100010ca3 PyObject_Call + 99
5   org.python.python              0x00000001000aecbd PyEval_EvalFrameEx + 13517
6   org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
7   org.python.python              0x00000001000b3129 fast_function + 297
8   org.python.python              0x00000001000ae995 PyEval_EvalFrameEx + 12709
9   org.python.python              0x00000001000b30c2 fast_function + 194
10  org.python.python              0x00000001000ae995 PyEval_EvalFrameEx + 12709
11  org.python.python              0x00000001000b30c2 fast_function + 194
12  org.python.python              0x00000001000ae995 PyEval_EvalFrameEx + 12709
13  org.python.python              0x00000001000ab57d PyEval_EvalCodeEx + 1725
14  org.python.python              0x00000001000364dc function_call + 364
15  org.python.python              0x0000000100010ca3 PyObject_Call + 99
16  org.python.python              0x000000010001de16 instancemethod_call + 166
17  org.python.python              0x0000000100010ca3 PyObject_Call + 99
18  org.python.python              0x00000001000b288d PyEval_CallObjectWithKeywords + 93
19  org.python.python              0x00000001000ed1a6 t_bootstrap + 70
20  libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
21  libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
22  libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 5 Crashed:
0   _CppBlockUtils.so              0x0000000104e3a3c6 StoredHeadHgtList::unserializeDBValue(BinaryRefReader&) + 470
1   _CppBlockUtils.so              0x0000000104e3a694 StoredHeadHgtList::unserializeDBValue(BinaryDataRef) + 52
2   _CppBlockUtils.so              0x0000000104e157b3 LMDBBlockDatabase::getStoredHeadHgtList(StoredHeadHgtList&, unsigned int) + 179
3   _CppBlockUtils.so              0x0000000104e1494e LMDBBlockDatabase::putBareHeader(StoredHeader&, bool) + 302
4   _CppBlockUtils.so              0x0000000104e94e25 Blockchain::putNewBareHeaders(LMDBBlockDatabase*) + 309
5   _CppBlockUtils.so              0x0000000104e4e131 BlockDataManager_LevelDB::loadDiskState(std::__1::function<void (BDMPhase, double, unsigned int, unsigned int)> const&, bool) + 2945
6   _CppBlockUtils.so              0x0000000104ea5af2 BlockDataManagerThread::run() + 578
7   _CppBlockUtils.so              0x0000000104ea57f9 BlockDataManagerThread::thrun(void*) + 9
8   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
9   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
10  libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Thread 6:
doug_armory
Sr. Member
****
Offline Offline

Activity: 255

Senior Developer - Armory


View Profile WWW
August 16, 2015, 11:22:32 PM
 #4580

It is thread 5:

Code:
Thread 5 Crashed:
0   _CppBlockUtils.so              0x0000000104e3a3c6 StoredHeadHgtList::unserializeDBValue(BinaryRefReader&) + 470
1   _CppBlockUtils.so              0x0000000104e3a694 StoredHeadHgtList::unserializeDBValue(BinaryDataRef) + 52
2   _CppBlockUtils.so              0x0000000104e157b3 LMDBBlockDatabase::getStoredHeadHgtList(StoredHeadHgtList&, unsigned int) + 179
3   _CppBlockUtils.so              0x0000000104e1494e LMDBBlockDatabase::putBareHeader(StoredHeader&, bool) + 302
4   _CppBlockUtils.so              0x0000000104e94e25 Blockchain::putNewBareHeaders(LMDBBlockDatabase*) + 309
5   _CppBlockUtils.so              0x0000000104e4e131 BlockDataManager_LevelDB::loadDiskState(std::__1::function<void (BDMPhase, double, unsigned int, unsigned int)> const&, bool) + 2945
6   _CppBlockUtils.so              0x0000000104ea5af2 BlockDataManagerThread::run() + 578
7   _CppBlockUtils.so              0x0000000104ea57f9 BlockDataManagerThread::thrun(void*) + 9
8   libsystem_pthread.dylib        0x00007fff91c5305a _pthread_body + 131
9   libsystem_pthread.dylib        0x00007fff91c52fd7 _pthread_start + 176
10  libsystem_pthread.dylib        0x00007fff91c503ed thread_start + 13

Ah ha. That is definitely Armory code.

Senior Developer -  Armory Technologies, Inc.
Pages: « 1 ... 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 [229] 230 231 232 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!