[unixODBC-dev] Segfault when utilizing libodbc with Asterisk

Stefan Radman Stefan.Radman at CTBTO.ORG
Fri May 18 09:59:05 BST 2007

> Ok, I don't know exactly how (or what) 2.2.12-1.el4s1 is, I guess its 
> based on the 2.2.12 tree, but as I know people started 
unixODBC-2.2.12-1.el4s1.1 is part of the CentOS WebStack of the CentOS
Plus Repository
It seems to be identical with an RPM in the Red Hat Application Stack
1.1 for RHEL4
The source RPM includes the official 2.2.12 tarball from Oct 2006 with 4
additional patches.

> -----Original Message-----
> From: unixodbc-dev-bounces at easysoft.com 
> [mailto:unixodbc-dev-bounces at easysoft.com] On Behalf Of Nick Gorham
> Sent: Friday, 18 May, 2007 10:35
> To: Development issues and topics for unixODBC
> Subject: Re: [unixODBC-dev] Segfault when utilizing libodbc 
> with Asterisk
> Leif Madsen wrote:
> > Evening all!
> >
> > I apologize now if I'm utilizing the wrong mailing list. I was
> > debating between support and the dev list, but the 
> description of the
> > dev list seemed more appropriate. I will be sure to correct this in
> > the future if I'm wrong :)
> No, this will do :-)
> >
> > I am utilizing unixODBC package (unixODBC and unixODBC-devel version
> > 2.2.12-1.el4s1.1) on CentOS 4.4, and have been seeing some random
> > segfaults of Asterisk when utilizing the libodbc libraries. The
> > developers of Asterisk have stated they believe it to be a 
> problem in
> > the libodbc driver, and the developers of the Progress (not
> > postgresql) database have fixed a similar issue apparently 
> for another
> > implementor I speak with regularly and his crashes seem to 
> have become
> > resolved. (I do not have the fix he received from the vendor, but if
> > you think it would be of use, then I can follow up with that
> > information.)
> Ok, I don't know exactly how (or what) 2.2.12-1.el4s1 is, I guess its 
> based on the 2.2.12 tree, but as I know people started 
> producing builds 
> before it was released your guess is as good as mine. I could 
> do with a 
> bit more information, what odbc driver are you using under 
> libodbc? Yes 
> any details from the postgres folk could help.
> The backtrace show two failures in different places, that makes me 
> suspect memory corruption somewhere. May be unixODBC, may be the odbc 
> driver under it, may be something else.
> I would get either the real released 2.2.12 or the current 
> 2.2.13 from 
> the ftp site, and build from source (making sure its building with 
> threads), try that, and see if it gives you any more information.
> Failing that, maybe something like valgrind would let you 
> find the place 
> the actual corruption happened, I suspect the crash you are 
> seing is the 
> result of a problem that happened at some point before the 
> actual crash.
> -- 
> Nick Gorham
> Easysoft Limited
> http://www.easysoft.com, http://www.unixODBC.org
> _______________________________________________
> unixODBC-dev mailing list
> unixODBC-dev at easysoft.com
> http://mail.easysoft.com/mailman/listinfo/unixodbc-dev

More information about the unixODBC-dev mailing list