[erlang-questions] r16b02 odbc-2.10.17 crash on bind NULL output value.

Saltanov, Alexey Alexey.Saltanov@REDACTED
Wed Feb 18 08:03:18 CET 2015


I try to execute some code:
{ok, Conn} = odbc:connect("user/pass@REDACTED", [{scrollable_cursors, off}, {auto_commit, on}, {binary_strings, on}]).
odbc:param_query (Conn, "begin ? := null; end;", [{{sql_varchar, 8000}, out, [<<"">>]}]).

And odbcserver crashes...
ODBC: received unexpected info: {tcp_closed,#Port<0.4260>}

GNU gdb (GDB) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /home/alex/src/odbc/priv/bin/odbcserver...done.
[New LWP 17872]
[New LWP 17873]

warning: Corrupted shared library list: 0x7f6c7f1f5000 != 0x0
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
Core was generated by `/home/alex/src/odbc/priv/bin/odbcserver'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x0000003c40a0df16 in _dl_fixup () from /lib64/ld-linux-x86-64.so.2
(gdb) bt
#0  0x0000003c40a0df16 in _dl_fixup () from /lib64/ld-linux-x86-64.so.2
#1  0x0000003c40a14695 in _dl_runtime_resolve () from /lib64/ld-linux-x86-64.so.2
#2  0x00007f6c7d5034f0 in ?? ()
#3  0x0000000000000000 in ?? ()

Why odbcserver crashes on binding NULL value into varchar output parameter?


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20150218/3d4f4766/attachment.htm>


More information about the erlang-questions mailing list