[asterisk-users] Re: Core Dump: create_transaction (p=0x0) atpbx_dundi.c:2787

[Douglas Garstang]

> -----Original Message-----
> From: Tony Mountifield [mailto:tony at softins.clara.co.uk]
> Sent: Wednesday, December 13, 2006 1:19 PM
> To: asterisk-users at lists.digium.com
> Subject: [asterisk-users] Re: Core Dump: create_transaction (p=0x0)
> atpbx_dundi.c:2787
> 
> 
> In article 
> <645FEC31A18FE54A8721500CDD55A7B6035D0C47 at mail.oneeighty.com>,
> Douglas Garstang <dgarstang at oneeighty.com> wrote:
> > Anyone seen this...? Is it a known issue?
> > 
> > I'd file a bug, but we're on 1.2.9.13, and every time I 
> file a bug and it isn't against the
> > latest code I get given crap for it. Given that most of the 
> time you don't know HOW to
> > reproduce a problem on the latest code anyway, not 
> accepting bugs from older versions does
> > the community no service, because potential bugs are never 
> accepted for submission.
> > 
> > (gdb) bt full
> > #0  0xb7da8d3c in mallopt () from /lib/libc.so.6
> > No symbol table info available.
> > #1  0xb7da7e3a in malloc () from /lib/libc.so.6
> > No symbol table info available.
> > #2  0xb7b30aa1 in create_transaction (p=0x0) at pbx_dundi.c:2787
> >         trans = (struct dundi_transaction *) 0x0
> 
> Hmmm, that will be a tricky one to track down. There's no 
> reason to get
> a core dump from within malloc() unless something else has previously
> stomped outside of its own malloced area, smashing the free list.
> 
> So the problem is likely not within create_transaction(), but caused
> sometime before, possibly in some completely unrelated code.
> 
> Is it repeatable, or just happens at random (or even just once)?

Only the one time so far.