[unixODBC-support] buffer overrun in extract_diag_error_w

Yakovets, Aleksey aleksey.yakovets at jpmorgan.com
Tue Mar 4 15:18:11 GMT 2014


All revisions of  __info.c (including trunk) seems to use bytes

From: unixodbc-support-bounces at mailman.unixodbc.org [mailto:unixodbc-support-bounces at mailman.unixodbc.org] On Behalf Of Nick Gorham
Sent: Tuesday, March 04, 2014 3:09 AM
To: Support for the unixODBC project
Subject: Re: [unixODBC-support] buffer overrun in extract_diag_error_w

On 03/03/14 22:20, Yakovets, Aleksey wrote:
Hi,
I ran into buffer overrun problem when an error message is too long ( longer than 1.5K - Vertica/ pyodbc/unix odbc2.3.1/RedHat stack)
What is the msg1 buffer length  in SQLGETDIAGRECW() /extract_diag_error_w - is it in bytes or in characters?

The code seems to be inconsistent with http://support.microsoft.com/kb/243526/EN-US

SQLERRORW/extract_sql_error_w  follow the same convention

Any help is greatly appreciated.

Hi,

I will take a look at this, but could you check 2.3.3pre to make sure its not already fixed.

--
Nick

This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.unixodbc.org/pipermail/unixodbc-support/attachments/20140304/cdb1ec96/attachment.html>


More information about the unixODBC-support mailing list