Re: SQLFreeStmt(hstmt, SQL_DROP); Failure ?
От | lothar.behrens@lollisoft.de |
---|---|
Тема | Re: SQLFreeStmt(hstmt, SQL_DROP); Failure ? |
Дата | |
Msg-id | 1164142898.048670.254240@h48g2000cwc.googlegroups.com обсуждение исходный текст |
Ответ на | Re: SQLFreeStmt(hstmt, SQL_DROP); Failure ? (Ludek Finstrle <luf@pzkagis.cz>) |
Список | pgsql-odbc |
Ludek Finstrle schrieb: > > Did someone knows, why the trace isn't activated ? > > Are you talking about mylog output or something else? I mean mylog. The function wich reports every function call and more. > > > Debug = 1 > > DebugFile = /Users/lothar/lbDMF.debug.log > > DebugFile isn't supported as I know. > Where are you looking for debug? It should be in /tmp directory named > something like mylog.<pid> I also have had a look at /tmp. There isn't such a file. This is because mylog_on is false: void mylog(char *fmt,...) { va_list args; char filebuf[80]; static FILE *LOGFP = NULL; ENTER_MYLOG_CS; if (mylog_on) { ... Do I have to activate these logging via ./configure ? But nevertheless, I think, I get a corrupted stack. In the case where I had used iodbc drivermanager this lead into the behaviour, that SQLFreeStmt didn't come back. Currently, with unixodbc drivermanager, I seem to have a corrupted heap :-( Would any log from the driver be helpful ? Regards, Lothar > > Regards, > > Luf > > ---------------------------(end of broadcast)--------------------------- > TIP 9: In versions below 8.0, the planner will ignore your desire to > choose an index scan if your joining column's datatypes do not > match
В списке pgsql-odbc по дате отправления: