Segfault upon SIGINT

[anonimal]

By submitting this issue, I confirm the following:

• I have read and understood the contributor guide.
• I have checked that the issue I am reporting can be replicated or that the feature I am suggesting is not present.
• I have checked opened or recently closed pull requests for existing solutions/implementations to my issue/suggestion.

Place an X inside the bracket to confirm

• I confirm.

---

Built against 7f8c04f
Simple backtrace attached.

[anonimal]

Another backtrace, this time quickly after startup.

[anonimal]

fe270c0 fixes segfault but only if client destination isn't actively used (e.g., start router, wait for integration but don't connect to IRC, ctrl-c, exits normally); otherwise, we have a garlic related segfault (backtrace attached).

[guzzijones]

wow. nice work anonimal. how you found this i have no idea. i hope to be as awesome as you some day.

[anonimal]

lol, @guzzijones you're too much 😄 I hope to be as awesome as you some day 😉

The backtrace said it all. I could've spent time with a custom deleter (or refactored elsewhere) but, since there is no current (and I mean current) reason to enforce pointer ownership in this particular area, I thought that a raw pointer would suffice for now (IMHO).