Skip to Content.
Sympa Menu

freetds - Re: [freetds] Segmentation fault on dbinit()

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Paul Andrews" <andrewsp AT andronics.com>
  • To: "'FreeTDS Development Group'" <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Segmentation fault on dbinit()
  • Date: Thu, 25 Oct 2007 20:32:57 +0100

Thanks James...very useful advice. I'll had recompiled from source on the
previous installation but will do so again tomorrow as well as run ldd. I
will post the backtrace should the error still occur.

Thanks again.

Paul.

-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of James K. Lowden
Sent: 25 October 2007 19:08
To: FreeTDS Development Group
Subject: Re: [freetds] Segmentation fault on dbinit()

Paul Andrews wrote:
> I can confirm that
> 1. dbinit is only called once.
> 2. fopen causes a segmentation fault

Hi Paul,

I'm starting to think this is an ABI problem.

> I sent the entire project over to a colleague who successfully debugged
> and ran the program on his 10.2 installation.

Good. That supports the notion that your code *and* FreeTDS are OK.

> I then decided to update to Suse 10.3 (complete format and new
> installation).
>
> Problem is still there.
...
> I have glibc 2.6.1-18.3, he has glibc 2.4-31.1
...
> Platform: Suse 10.2 / 10.3 using rpm's from OpenSuse.org

Did you build FreeTDS from source on the 10.3 box? If you're using
binaries compiled for another glibc, that could conceivably explain a
fault in fopen(3). In that case, though, it's the shared objects you'd be
interested in. Try ldd(1) on both system to see what your program is
using.

See also the gnu libc faq:
http://www.gnu.org/software/libc/FAQ.html#s-1.17,

The standard remedy to broken binaries is to build good ones. Then do
"make check" and watch everything work. ;-)

(You might try having your friend compile your test program and running it
on your machine. But that could only prove a negative; if it worked, it
wouldn't tell us much.)

If you built from scratch on your machine and get a failure in the first
unit test in fopen(3), I would be interested in seeing the backtrace. I
don't know what I could do about it, but it would be interesting!

HTH.

--jkl
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.10/1092 - Release Date: 25/10/2007
13:14


No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.503 / Virus Database: 269.15.10/1092 - Release Date: 25/10/2007
13:14






Archive powered by MHonArc 2.6.24.

Top of Page