This was fixed in version 2.2.14p2-3 and later of the unixodbc package.
** Changed in: unixodbc (Ubuntu)
Status: Confirmed = Fix Released
** Bug watch added: Debian Bug tracker #607895
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607895
** Also affects: unixodbc (Debian) via
** Changed in: unixodbc (Debian)
Status: Unknown = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unixodbc in Ubuntu.
https://bugs.launchpad.net/bugs/724517
Title:
isql segfaults in batch mode
To manage
I don't know why I didn't see this before, but the bug seems to come
from an extra variable declaration in an inner scope. Removing that
declaration fixed the problem.
** Patch added: Patch to remove errant variable declarations
The attachment Patch to remove errant variable declarations of this
bug report has been identified as being a patch. The ubuntu-reviewers
team has been subscribed to the bug report so that they can review the
patch. In the event that this is in fact not a patch you can resolve
this situation by
** Changed in: unixodbc (Ubuntu)
Importance: Low = Medium
** Changed in: unixodbc (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to unixodbc in ubuntu.
** Attachment added: Shows isql crashing in batch mode, with no commands
having been entered, as soon as ctrl-d is pressed.
https://bugs.launchpad.net/ubuntu/+source/unixodbc/+bug/724517/+attachment/1878692/+files/gdb-isql.txt
--
You received this bug notification because you are a member
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a backtrace following the
instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
the backtrace (as an attachment) to the bug report. This will greatly
help us in tracking down
