Fix a variety of memory corruption/assertion errors
authorMatthew Jordan <mjordan@digium.com>
Sun, 26 May 2013 04:47:17 +0000 (04:47 +0000)
committerMatthew Jordan <mjordan@digium.com>
Sun, 26 May 2013 04:47:17 +0000 (04:47 +0000)
commitfe3ca5401f2543bcc59d73de0ffd779112322d6c
treed4d7ee76fe9f3b032b7d40ef57861cecf93eeb12
parent97c6062dfc528d60c7115cca1a4a4e7c44c882f6
Fix a variety of memory corruption/assertion errors

* Initialize a Stasis-Core message type prior to initializing a caching topic.
  The caching topic will attempt to use the message type.
* Don't attempt to publish Stasis-Core messages from remote console connections.
  They aren't the main process; they shouldn't attempt to behave as it (they also
  don't have the infrastructure to do so)
* Don't treat a JSON object as an ao2 object (whoops)
* In asterisk.c, ref bump the JSON even package that is distributed with the
  event meta data. The callers assume that they own the reference, and the packing
  routine steals references.

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@389785 65c4cc65-6c06-0410-ace0-fbb531ad65f3
main/asterisk.c
main/devicestate.c
res/res_fax.c