That's not useful, you need to collect the core and run gdb on it.


On Thu, Oct 27, 2011 at 2:07 PM, Cliff Wells <cliff@develix.com> wrote:
On Thu, 2011-10-27 at 18:42 +0200, Hynek Cihlar wrote:
> Did you try to locate the source of the segmantation fault? At least
> the module.

Here's a sample:

freeswitch[30818]: segfault at 710 ip 00007f343516b491 sp 00007f33f17b7fc0 error 4 in psqlodbcw.so[7f3435126000+7d000]

I know it's pointing at the PostgreSQL ODBC driver (and this may, in
fact, be the case), but it's hard to know whether the driver itself is
the issue, or whether mishandling of the driver is at fault.

Also, in 2.3.0, unixODBC stopped shipping their own PostgreSQL driver
and now use the one shipped with PostgreSQL instead, so this may have an
impact on stability.  In any case, until I'm able to do more testing
with 2.3.0 I'm just speculating.



--
Anthony Minessale II

FreeSWITCH http://www.freeswitch.org/
ClueCon http://www.cluecon.com/
Twitter: http://twitter.com/FreeSWITCH_wire

AIM: anthm
MSN:anthony_minessale@hotmail.com
GTALK/JABBER/PAYPAL:anthony.minessale@gmail.com
IRC: irc.freenode.net #freeswitch

FreeSWITCH Developer Conference
sip:888@conference.freeswitch.org
googletalk:conf+888@conference.freeswitch.org
pstn:+19193869900