Bug 18475 - Configuring myodbc connector implied a crash
Summary: Configuring myodbc connector implied a crash
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: All Packagers
QA Contact:
URL:
Whiteboard: MGA5TOO
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-17 20:10 CEST by papoteur
Modified: 2021-01-27 07:26 CET (History)
1 user (show)

See Also:
Source RPM: mysql-connector-odbc-5.3.2-3.mga6
CVE:
Status comment:

Attachments
Backtrace of the error (6.77 KB, text/plain)
2016-05-17 21:05 CEST, papoteur 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Description papoteur 2016-05-17 20:10:10 CEST 
Description of problem:
When I try to declare the mysql odbc connector using myodbc-installer, I get an error:
** Error in `myodbc-installer': free(): invalid pointer: 0x0000000001c1eb18 ***

Version-Release number of selected component (if applicable):
mysql-connector-odbc-5.3.2-2.mga5

How reproducible:
myodbc-installer -a -d -n "MySQL ODBC" -t "Driver64=/usr/li^C4/libmyodbc5w.so;SETUP=/usr/lib64/libmyodbc5S.so"
Comment 1 papoteur 2016-05-17 21:05:54 CEST 
Created attachment 7802 [details]
Backtrace of the error
Comment 2 Marja Van Waes 2016-05-19 09:52:01 CEST 
Assigning to all packagers collectively, since there is no maintainer for this package.

CC: (none) => marja11
Assignee: bugsquad => pkg-bugs

Comment 3 papoteur 2016-07-15 22:44:55 CEST 
Fedora seems to applied a patch:
https://bugzilla.redhat.com/show_bug.cgi?id=1173783
papoteur 2016-07-16 06:52:07 CEST

Whiteboard: (none) => MGA5_TOO
Version: 5 => Cauldron

papoteur 2016-07-16 06:53:30 CEST

Source RPM: mysql-connector-odbc-5.3.2-2.mga5 => mysql-connector-odbc-5.3.2-3.mga6

Rémi Verschelde 2016-07-16 15:02:47 CEST

Whiteboard: MGA5_TOO => MGA5TOO

Comment 4 papoteur 2021-01-27 07:26:24 CET 
This package is no more in Mageia 7.
Closing

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.