[asterisk-dev] Mixmonitor causes segfault with trunk

[Julian Lyndon-Smith]

using the latest svn trunk (41318) MixMonitor causes a segfault soon 
after it is started. Bt full give the following (it's the same in all 
three cores I've looked at):

Should I raise a bug, or are people aware already ?

#0  0x080825b3 in ast_channel_spy_read_frame (spy=0x8aea558, 
samples=160) at channel.c:4136
         result = (struct ast_frame *) 0x0
         read_buf = {-5, -3}
         write_buf = {2, -11}
         read_frame = (struct ast_frame *) 0x32
         write_frame = (struct ast_frame *) 0xbcc8b
         need_dup = 1156937475
         stack_read_frame = {frametype = 2, subclass = 64, datalen = 
320, samples = 160, mallocd = 0, mallocd_hdr_len = 0,
   offset = 0, src = 0x0, data = 0xb76dd170, delivery = {tv_sec = 0, 
tv_usec = 0}, frame_list = {next = 0x0},
   has_timing_info = 0, ts = 0, len = 0, seqno = 0}
         stack_write_frame = {frametype = 2, subclass = 64, datalen = 
320, samples = 160, mallocd = 0,
   mallocd_hdr_len = 0, offset = 0, src = 0x0, data = 0xb76dd020, 
delivery = {tv_sec = 0, tv_usec = 0}, frame_list = {
     next = 0x0}, has_timing_info = 0, ts = 0, len = 0, seqno = 0}
#1  0x003dc684 in mixmonitor_thread (obj=0x8aea558) at app_mixmonitor.c:184
         next = (struct ast_frame *) 0x0
         write = 1
         mixmonitor = (struct mixmonitor *) 0x8aea558
         f = (struct ast_frame *) 0x0
#2  0x080e52e3 in dummy_start (data=0x8aeabe8) at utils.c:538
         _buffer = {__routine = 0x8067985 <ast_unregister_thread>, __arg 
= 0xb76ddbb0, __canceltype = 0, __prev = 0x0}
         ret = (void *) 0x8e166c
         a = {start_routine = 0x3dc5ec <mixmonitor_thread>, data = 
0x8aea558,
   name = 0x8aeb4b0 "mixmonitor_thread    started at [  315] 
app_mixmonitor.c launch_monitor_thread()"}