Bug 78879 - DataManager crashed when browse the database talbes.
Summary: DataManager crashed when browse the database talbes.
Status: CLOSED DUPLICATE of bug 77635
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mysql
Version: 8.0
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Patrick Macdonald
QA Contact: David Lawrence
URL: http://bugs.debian.org/cgi-bin/bugrep...
Depends On:
TreeView+ depends on / blocked
Reported: 2002-12-02 18:06 UTC by Need Real Name
Modified: 2007-04-18 16:48 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2006-02-21 18:50:15 UTC

Attachments (Terms of Use)

Description Need Real Name 2002-12-02 18:06:51 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
Error Messages gived by DataManager:

DataManager: relocation error: /usr/lib/libmyodbc.so: undefined symbol:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.start mysql
2.setup myodbc driver and system DNS source in ODBCConfig
3.test ODBC with DataManager
    1). Expand ODBC
    2). Expand System Data Sources
    3). Expand mysql(for mysql database), input the account and passwd
    4). Expand Tables --- crashed.

Actual Results:  DataManager: relocation error: /usr/lib/libmyodbc.so: undefined
symbol: _init_dynamic_array

Expected Results:  Browse Tables, and then, browse my table ...

Additional info:

Debian fixed it already.

Comment 1 Fernando Nasser 2003-02-13 14:58:47 UTC
This is a binary incompatibility problem between the libmysqlclient10 and
libmysqlclient9 (as the referenced Debian bug shows).

Changing component to mysql. We have a mysqlclient9 component -- was that just
mysqlclient (without the version qualification) I would have sent it there.

Comment 2 Patrick Macdonald 2003-02-13 17:14:16 UTC
This is a duplicate of 77635

*** This bug has been marked as a duplicate of 77635 ***

Comment 3 Red Hat Bugzilla 2006-02-21 18:50:15 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.