|Summary:||ASTERISK-15534: Every time I type "odbc show" it crashes in the next few seconds|
|Reporter:||Private Name (falves11)||Labels:|
|Date Opened:||2010-01-27 17:42:06.000-0600||Date Closed:||2011-06-07 14:00:43|
|Environment:||Attachments:||( 0) crassh161_odbc.txt|
|Description:||The same happens with version 1.6.2|
|Comments:||By: Tilghman Lesher (tilghman) 2010-01-28 01:29:11.000-0600|
Please show that your ODBC driver is not at fault.
By: Private Name (falves11) 2010-01-28 02:31:15.000-0600
how can I do that or not do that?
I use of course UNIXodbc and freetds, which are pretty much tested by the worldwide community. Besides, the trace submitted should show where the issue is. I remember, by the way, that one engineer from the maker of UNIXodbc, once mentioned that what asterisk does when you type "odbc show" was wrong. That was at least 3 years ago.
By: Tilghman Lesher (tilghman) 2010-01-28 09:07:50.000-0600
Based upon the details in your report, I have to conclude that it's the FreeTDS driver, since it is crashing in a routine that normally does not crash, with the same arguments. Unless you can show otherwise, we're done with this report.
By: Private Name (falves11) 2010-01-28 09:12:04.000-0600
In version 1.4.X the same command, ceteris paribus, does not crash. is this an indication that something is not right in 1.6.X?
Note: "ceteris paribus" means, "everything else remaining constant"
however, if you give more insight as to why do you think the culprit is the freetds driver, I will post the problem to the freetds list.
By: Leif Madsen (lmadsen) 2010-03-23 10:33:22
Closing per Tilghman's comments.