program crashes saying "undefined symbol: strfill"

Bug #1010044 reported by Chris Curvey
38
This bug affects 6 people
Affects Status Importance Assigned to Milestone
myodbc (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

program runs fine for a while, but then crashes looking for the strfill function.

/usr/bin/python: symbol lookup error:
/usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so: undefined symbol: strfill

I raised this with the MySQL folks, but they said it was a packaging issue. See http://bugs.mysql.com/bug.php?id=65509. Note especially the comment about "Surely, that whole problem occurred because the driver binary depended on libmysqlclient.so."

There is also something (possibly related) in the debian bugs, but I don't really understand what happened with this. See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661422

I'm not sure if this is something that is to be reported to ubuntu or debian, please advise if it should be reported to debian.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: libmyodbc 5.1.10-1
ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu8
Architecture: amd64
Date: Thu Jun 7 10:29:05 2012
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
SourcePackage: myodbc
UpgradeStatus: Upgraded to precise on 2012-05-31 (7 days ago)

Revision history for this message
Chris Curvey (chris-0zxvj9hhx1hzo5xiyh) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in myodbc (Ubuntu):
status: New → Confirmed
Revision history for this message
Marc Vanhoomissen (mvh) wrote :

I can reproduce the problem using the following steps using the same configuration (+ python 2.7.3 and pyodbc) and the following instructions:

marc@servamtex:~$ python
Python 2.7.3 (default, Aug 1 2012, 05:14:39)
[GCC 4.6.3] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyodbc as p
>>> DB=p.connect('DSN=Veramtex')
>>> for l in DB.execute("select now()"):
... for c in l:
... print c
...
2012-09-06 12:52:26
>>> for l in DB.execute("select date(now())"):
... for c in l:
... print c
...
python: symbol lookup error: /usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so: undefined symbol: strfill
marc@servamtex:~$ python

Revision history for this message
Mazman (laurent-mazuel) wrote :

I confirm this bug on a debian wheezy install:
$ apt-cache show libmyodbc
Package: libmyodbc
Source: myodbc
Version: 5.1.10-2+deb7u1
Installed-Size: 373
Maintainer: Steve Langasek <email address hidden>
Architecture: amd64

I reproduce it using the C interface of ODBC, also using "date" accessing.

However, I'm not sure that the MySQL team have right. In a debian squeeze, the driver is linked against the dynamic library too:
# ldd /usr/lib/odbc/libmyodbc.so | grep libmysql
 libmysqlclient_r.so.16 => /usr/lib/libmysqlclient_r.so.16 (0x00007f2700fbd000)

as in my wheezy:
$ ldd /usr/lib/x86_64-linux-gnu/odbc/libmyodbc.so | grep mysql
 libmysqlclient.so.18 => /usr/lib/x86_64-linux-gnu/libmysqlclient.so.18 (0x00007f04e78b4000)

But the same code works perflectly in Squeeze, not in Wheezy

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.