On Fri, Dec 28, 2012 at 9:36 AM, Jerry Geis <[email protected]> wrote:
> If you got the segfault, then recompiled with debug info, then the > addresses in the segfault are no longer relevant to the binary you have. > > Are you getting the segfault repeatedly? If so, then just wait for it to > happen again with the debug info and work with that, and/or the core file > that Asterisk creates. > > If you can't reproduce the segfault, unfortunately that is just the way of > things sometimes. Could be a random bit-flip in a stick of memory. > > In either case, if that segfault line was generated by a non-debug asterisk > build, it isn't really useful to you. > > I was able with gdb to set a break point at the address of the > instruction pointer: > > ip 00296f96 > > This is in memcpu_iax32, which is called from sip_alloc() which is called > from transmiter_register() > > Yes, but that probably isn't where it was in the original binary. Now that you've recompiled it including debug info, you have a different binary, with different addresses. Chances are slim that this is actually where the crash occurred. Reproduce the segfault with the new debug binary. > ?? > > Jerry > > > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > asterisk-users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > -- -Chris Harrington ACSDi Office: 763.559.5800 Mobile Phone: 612.326.4248
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
