[Asterisk-Users] app_dbodbc segfault

[brian k. west]

I honestly don't have any incentive to fix this :(  Waiting on res_data two
write a res_data aware version.

bkw

----- Original Message ----- 
From: "Mike Machado" <mike at homelandtel.com>
To: <asterisk-users at lists.digium.com>
Sent: Friday, April 30, 2004 5:19 PM
Subject: RE: [Asterisk-Users] app_dbodbc segfault


> Yes, as of this morning.
>
> On Fri, 2004-04-30 at 15:56, brian wrote:
> > WOAH!!! You using latest cvs?
> >
> > bkw
> >
> > > -----Original Message-----
> > > From: asterisk-users-admin at lists.digium.com [mailto:asterisk-users-
> > > admin at lists.digium.com] On Behalf Of Mike Machado
> > > Sent: Friday, April 30, 2004 5:39 PM
> > > To: asterisk-users at lists.digium.com
> > > Subject: RE: [Asterisk-Users] app_dbodbc segfault
> > >
> > >
> > > It is producing 2 core files. Here are the backtraces of each:
> > >
> > >
> > > #0  0x402d5156 in create_addr (r=0x81a9658, peer=0xbd7fdd24
> > > "9258004633") at chan_sip.c:968
> > > 968                             memcpy(&r->sa.sin_addr, hp->h_addr,
> > > sizeof(r->sa.sin_addr));
> > > (gdb) bt
> > > #0  0x402d5156 in create_addr (r=0x81a9658, peer=0xbd7fdd24
> > > "9258004633") at chan_sip.c:968
> > > #1  0x402e88b7 in sip_request (type=0xbd7fe524 "SIP", format=4,
> > > data=0xbd7fe2d4) at chan_sip.c:6229
> > > #2  0x0805a1fd in ast_request (type=0xbd7fe524 "SIP", format=68,
> > > data=0xbd7fe2d4) at channel.c:1767
> > > #3  0x40524f4f in dial_exec (chan=0x81b2b88, data=0xbd7fe854) at
> > > app_dial.c:651
> > > #4  0x08064f8c in pbx_exec (c=0x81b2b88, app=0x80e5f88,
data=0xbd7fe854,
> > > newstack=1) at pbx.c:413
> > > #5  0x08067043 in pbx_extension_helper (c=0x81b2b88, context=0x81b2ce0
> > > "macro-sipexten", exten=0x81b2dd4 "s", priority=5,
> > >     callerid=0x814e908 "9252533152", action=1) at pbx.c:1195
> > > #6  0x0806dcee in ast_spawn_extension (c=0x81b2b88, context=0x81b2ce0
> > > "macro-sipexten", exten=0x81b2dd4 "s", priority=5,
> > >     callerid=0x814e908 "9252533152") at pbx.c:1679
> > > #7  0x406e24a8 in macro_exec (chan=0x81b2b88, data=0xbd7ff2a4) at
> > > app_macro.c:140
> > > #8  0x08064f8c in pbx_exec (c=0x81b2b88, app=0x8145e70,
data=0xbd7ff2a4,
> > > newstack=1) at pbx.c:413
> > > #9  0x08067043 in pbx_extension_helper (c=0x81b2b88, context=0x81b2ce0
> > > "macro-sipexten", exten=0x81b2dd4 "s", priority=1,
> > >     callerid=0x814e908 "9252533152", action=1) at pbx.c:1195
> > > #10 0x08067d7d in ast_pbx_run (c=0x81b2b88) at pbx.c:1679
> > > #11 0x404d0480 in ss_thread (data=0x81b2b88) at chan_zap.c:4395
> > > #12 0x400210ba in pthread_start_thread () from /lib/libpthread.so.0
> > >
> > >
> > >
> > >
> > > #0  0x400c8781 in kill () from /lib/libc.so.6
> > > (gdb) bt
> > > #0  0x400c8781 in kill () from /lib/libc.so.6
> > > #1  0x40023e5e in pthread_kill () from /lib/libpthread.so.0
> > > #2  0x40024339 in raise () from /lib/libpthread.so.0
> > > #3  0x400c9be1 in abort () from /lib/libc.so.6
> > > #4  0x4010fa30 in malloc_set_state () from /lib/libc.so.6
> > > #5  0x4010da29 in free () from /lib/libc.so.6
> > > #6  0x080968ba in el_end (el=0x80d62f8) at el.c:125
> > > #7  0x0808572c in quit_handler (num=15, nice=0, safeshutdown=1,
> > > restart=0) at asterisk.c:552
> > > #8  0x08088531 in __quit_handler (num=15) at asterisk.c:600
> > > #9  0x40023f54 in pthread_sighandler () from /lib/libpthread.so.0
> > > #10 0x400c86b8 in sigaction () from /lib/libc.so.6
> > > #11 0x08084daf in listener (unused=0x0) at asterisk.c:298
> > > #12 0x400210ba in pthread_start_thread () from /lib/libpthread.so.0
> > >
> > >
> > > Looks to me like its in no way related to the dbodbc stuff...
> > >
> > > Let me know if there is anything else you need me to do.
> > >
> > >
> > >
> > > On Fri, 2004-04-30 at 13:04, Philipp von Klitzing wrote:
> > > > Hi!
> > > >
> > > > > bt = Back trace?
> > > > >
> > > > > My gdb experience is limited. I tried to do
> > > > >
> > > > > gdb
> > > > > run -vvvvvvvvv
> > > > >
> > > > > but it took like 10 minutes for asterisk to fully start, and even
> > > then,
> > > > > it did not seem to be starting correctly.
> > > > >
> > > > > What is the best way to get a back trace from asterisk?
> > > >
> > > > Look here:
> > > > http://www.voip-info.org/tiki-index.php?page=Asterisk debugging
> > > >
> > > > Cheers, Philipp
> > > >
> > > > _______________________________________________
> > > > Asterisk-Users mailing list
> > > > Asterisk-Users at lists.digium.com
> > > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > > > To UNSUBSCRIBE or update options visit:
> > > >    http://lists.digium.com/mailman/listinfo/asterisk-users
> > >
> > > _______________________________________________
> > > Asterisk-Users mailing list
> > > Asterisk-Users at lists.digium.com
> > > http://lists.digium.com/mailman/listinfo/asterisk-users
> > > To UNSUBSCRIBE or update options visit:
> > >    http://lists.digium.com/mailman/listinfo/asterisk-users
> >
> >
> > _______________________________________________
> > Asterisk-Users mailing list
> > Asterisk-Users at lists.digium.com
> > http://lists.digium.com/mailman/listinfo/asterisk-users
> > To UNSUBSCRIBE or update options visit:
> >    http://lists.digium.com/mailman/listinfo/asterisk-users
>
> _______________________________________________
> Asterisk-Users mailing list
> Asterisk-Users at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-users
> To UNSUBSCRIBE or update options visit:
>    http://lists.digium.com/mailman/listinfo/asterisk-users
>