Exception when closing application in debug mode

[stoffman]

I recently upgraded postgresql client library version from V13 to V15.

Everything works except when closing the application in *debug* mode I get an expectation "EXTERNAL Access Violation" .

I recreated this exception with the most simple application with the latest ZEOS8.0 version (The error also presented in version of ZEOS from a year ago)

It could be a problem with Lazarus but I don't really know how to debug this. Ideas?

Windows 10/Lazarus 2.2.4/ZEOS8.0 latest

Thanks

[marsupilami]

I recently upgraded postgresql client library version from V13 to V15.

Maybe it isn't a problem in Zeos but in the PostgreSQL client library? What happens if you use the old client library?

Honestly I would ignore the problem if it only is visible in the debugger.

[stoffman]

The old library works perfectly.

I never said it is a zeos problem, it can be the client library problem or lazarus problem too.

I'm looking for ideas on how to debug this.

[marsupilami]

As I said - I would ignore the problem since it is only visible in the debugger.

The message seems to imply that the access violation happens during the last phases of the tear down of the application where FPC already has given control over access violations back to the operating system.

It might be a good idea to ask on the Lazarus Forums, because there might be people that have more ideas about debugging the whole thing.

Also you might want to try to run the Zeos Test Suites in 64 Bits with your library and server to see if it produces any access violations that we can try to debug. That might also solve your problem.

But then it also could be a problem with the new client library. So having a minimum working example that raises the problem could also help. We could see what calls are made into the POsgreSQL client library and the see if we can find some documentation about changed behavior or if we can generate a test case that can be submitted as a bug to PostgreSQL.

With best regards,

Jan

[aehimself]

This sounds surprisingly similar to one of my first issues I ever posted about.
I stand by Jan, try a different version of the library; that provided solution to me at the end.