*** buffer overflow detected ***: /usr/lib64/R/bin/exec/R terminated on R 2.6.2 to 2.8.0: logging a bug?
Prof Brian Ripley wrote:
On Fri, 31 Oct 2008, Peter Dalgaard wrote:
Corrado wrote:
I apologise .... The dsn is not empty, the database the dsn connects to is empty! You get the same error when connecting to a populated database.
Do I? I wouldn't know... (You are _still_ not providing steps to reproduce the situation!) The actual maintainer might know, though, so wait for him to chime in.
He cannot reproduce this, on a Fedora 8 system with buffer overflow detection enabled and PostgreSQL 8.2.10 (the one that Fedora supplies). As the error is from the PostgreSQL ODBC driver, it is most likely a bug in that driver (and there is a long history of problems with PostgreSQL ODBC drivers, especially on 64-bit systems). Note that the error is pretty clearly in /usr/lib64/libodbcpsql.so.2 calling sprintf,
Oops. I should of course have said that the problem was in RODBC or further down the chain. Apologies.
and the buffer passed from RODBC has a length specified (correctly) in the SQLGetInfo call. Thus using sprintf on _that_ buffer would of itself be an error. So there is no evidence here of a 'serious problem with RODBC' (and many other people are using it on Linux systems with PostgreSQL, and no one else has reported any such issue).
O__ ---- Peter Dalgaard ?ster Farimagsgade 5, Entr.B c/ /'_ --- Dept. of Biostatistics PO Box 2099, 1014 Cph. K (*) \(*) -- University of Copenhagen Denmark Ph: (+45) 35327918 ~~~~~~~~~~ - (p.dalgaard at biostat.ku.dk) FAX: (+45) 35327907