Browse Source
We have to do a dance when we get a reconnect in openingd, because we don't normally expect to free both owner and peer. It's a layering violation: freeing a peer should clean up the owner's pointer to it, to avoid a double free, and we can eliminate this dance. The free order is now different, and the test_reconnect_openingd was overprecise. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>ppa-0.6.1
Rusty Russell
7 years ago
committed by
Christian Decker
3 changed files with 19 additions and 15 deletions
Loading…
Reference in new issue