<
jonasschnelli>
Do we link libdbus dynamic for our gitian builds?
<
@wumpus>
jonasschnelli: I think qt will always dlopen it at run time
<
@wumpus>
AFAIK we don't link to libdbus at all
<
GitHub193>
bitcoin/master facb6c0 MarcoFalke: [qa] mininode: fail on send_message instead of silent return
<
GitHub193>
bitcoin/master ed2cd59 MarcoFalke: Merge #8214: [qa] mininode: fail on send_message instead of silent return...
<
jonasschnelli>
Hmm... just got: bitcoind: sync.cpp:125: void potential_deadlock_detected(const std::pair<void*, void*>&, const LockStack&, const LockStack&): Assertion `onlyMaybeDeadlock' failed.
<
jonasschnelli>
Aborted
<
jonasschnelli>
I though we have fixed this in master?
<
sipa>
jonasschnelli: not if there is an actual possible deadlocm
<
@wumpus>
that looks like a legit deadlock
<
@wumpus>
cs_vRecvMsg,cs_main,cs_filter,cs_vSend versus cs_vSend,cs_main, cs_inventory,cs_filter
<
@wumpus>
what version is that traceback from?
<
sipa>
MarcoFalke commented on the addednode refactor with that, maybe he has some indication that that's the cause? i'll investigate shortly
<
@wumpus>
ok, I was looking at the line numbers in master and ending up in really strange places in the code
<
sipa>
well, that refactor was merged
<
MarcoFalke>
Sry, I guess jonasschnelli was running 4286f43025149cf44207c3ad98e4a1f068520ada. Not current master
<
jonasschnelli>
MarcoFalke, sipa: I was running 37c98307ac7645412ac153e376e6e1020d867202
<
jonasschnelli>
and again. node stopped
<
jonasschnelli>
same lockorder
<
jonasschnelli>
I'll try again and if will update to master after next try