[psqlodbc-Bugs][1002767] Fatal exception error after running some queries - Mailing list pgsql-odbc
From | |
---|---|
Subject | [psqlodbc-Bugs][1002767] Fatal exception error after running some queries |
Date | |
Msg-id | 20150202183903.0C05C1BB615D@pgfoundry.org Whole thread Raw |
List | pgsql-odbc |
psqlodbc-Bugs item #1002767, was changed at 2015-02-02 20:38 by Heikki Linnakangas You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1002767&group_id=1000125 Or by replying to this e-mail entering your response between the following markers: #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ (enter your response here, only in plain text format) #+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+#+ Status: Closed Priority: 3 Submitted By: Andrus Moor (kobruleht) Assigned to: Nobody (None) Summary: Fatal exception error after running some queries Category: None Group: None Resolution: Out of Date Category: None Group: None Resolution: None Initial Comment: To reproduce: Run some queries from Microsoft Visual FoxPro 9.0 SP1 against ODBC driver Log file containing queries and data is included. Observed: FoxPro crashes with access violation error. Fatal error: Exception code=C0000005 @ 14:23:46. Error log file: C:\eetasoft\algus\VFP9Rerr.log Called from - read_events line 0 { c:\eetasoft\algus\alguss.exe} Called from - alguss line 0 { c:\eetasoft\algus\alguss.exe} Reproducible: This is reproducible always in different computers. I can create exact repro if required. ---------------------------------------------------------------------- >Comment By: Heikki Linnakangas (hlinnaka) Date: 2015-02-02 20:38 Message: Oh, ok. If you could enable the Windows ODBC tracing option and send over the generated log, that might help. I'm not too excitedabout testing this with FoxPro, but I could try to reproduce the same sequence of calls with a little test program,based on the trace log. Could you also set Debug=1 in the driver config and send over the mylog_* files it generates, please? ---------------------------------------------------------------------- Comment By: Andrus Moor (kobruleht) Date: 2015-01-22 15:02 Message: I verified that this issue still occurs in 09.03.0400 I occurs after some time after viewing different queries. There are no exact steps yet. After running application and working working with it it occurs after some time. Re-running application and re-entering last commands does not reproduce it. It occurs again after some time. I can install odbc driver with advanced logging and send log if this helps. Using 32 bit odbc driver in Windows 7 x64 ---------------------------------------------------------------------- Comment By: Heikki Linnakangas (hlinnaka) Date: 2015-01-22 09:24 Message: Hiroshi may have fixed this per the comment, and we have no reproducer script. Probably not an issue anymore.. ---------------------------------------------------------------------- Comment By: Andrus Moor (kobruleht) Date: 2007-04-05 22:39 Message: This probem exists in last snapshot also. Log included. It seems that fatal exception occurs inside closed source product, not inside driver. I'm no idea how you can research this. I created server account for you so you can try without installing database. How to send logon credidentials by e-mail ? ---------------------------------------------------------------------- Comment By: Hiroshi Inoue (hinoue) Date: 2007-04-04 04:33 Message: I found a buffer overrun bug. It may be related to your problem. Could you try the snapshot driver ? regards Hiroshi Inoue ---------------------------------------------------------------------- Comment By: Hiroshi Inoue (hinoue) Date: 2007-03-27 05:47 Message: Could you send me the reproducible example ? It would be better if it's more simpler. regards, Hiroshi Inoue ---------------------------------------------------------------------- You can respond by visiting: http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1002767&group_id=1000125
pgsql-odbc by date: