summaryrefslogtreecommitdiff
path: root/doc/design/assistant/blog/day_116__the_segfault.mdwn
blob: 47633454a17a1b702deabcd78aefe92d818d6ced (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
Continuing to flail away at this XMPP segfault, which turned out not to be
fixed by bound threads. I managed to make a fairly self-contained and small
reproducible test case for it that does not depend on the network.
Seems the bug is gonna be either in the Haskell binding for GNUTLS,
or possibly in GNUTLS itself.

Update: John was able to fix it using my testcase! It was a GNUTLS
credentials object that went out of scope and got garbage collected.
I think I was seeing the crash only with the threaded runtime because
it has a separate garbage collection thread.

----

Arranged for the XMPP thread to restart when network connections
change, as well as when the webapp configures it.

Added an alert to nudge users to enable XMPP. It's displayed after adding a
remote in the cloud.

[[!img /assistant/xmppnudge.png]]

----

So, the first stage of XMPP is done. But so far all it does is push
notification. Much more work to do here.