<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<blockquote type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;">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.</pre>
</blockquote>
I was able with gdb to set a break point at the address of the
instruction pointer:<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<pre style="color: rgb(0, 0, 0); font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px;"> ip 00296f96
This is in memcpu_iax32, which is called from sip_alloc() which is called from transmiter_register()
??
Jerry
</pre>
<br>
</body>
</html>