Note that this occurs specifically because of the use of an *empty*
Setup64 line. If you don't configure a 'Setup64' setting at all,
unixodbc already falls back to 'Setup' correctly.
You're right that UnixODBC should do something more sensible to avoid
triggering the library assertion.
** Change
** Changed in: unixodbc (Ubuntu)
Status: Incomplete => Confirmed
** Changed in: unixodbc (Ubuntu)
Status: Confirmed => In Progress
** Changed in: unixodbc (Ubuntu)
Status: In Progress => Confirmed
--
ODBCConfig fails on configure existing data source
https://bugs.launchpad.
Thank you for interesting of this bug!
I've doing some experiments and here are the results:
This is not reproduced on clean installation of Ubuntu Karmic i386. The
package version is same, the steps are same, but works as expected. But,
on my Ubuntu Jaunty (x86_64) it is 100% reproducible. The d
Thank you for taking the time to report this bug and helping to make Ubuntu
better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as
detailed as possible.
This will help us to find and resolve the problem.
** Changed
