@Axel-Spoerl said in A Strange Qt and postgresql problem ! when using Kaspersky:

If everything is configured properly and you use pgsql > 10.7, the only idea I have is that Kaspersky (partly) blocks network traffic coming from an executable, which it doesn't know. But that's where my knowledge ends and you have to turn to the Kaspersky support.

Thank You so much bro <3 for great support
by the way i am using postgresql version 14 the latest one

i agree with you there's a problem on kaspersky they partly affect any unsigned software when connecting to postgresql ... (kaspersky set my tested softwares as (low restricted which is the best group when application doesn't have digital signature) in application control

Low Restricted. This group includes applications for which the following conditions are met: Applications are not digitally signed by trusted vendors. Applications are not recorded in the trusted applications database of Kaspersky Security Network.

One more thing: this should have been one of my first things I tried, but I ran the debugger and got the following message - "The inferior stopped because it received a signal from the operating system
Signal name: SIGSEGV
Signal meaning: Segmentation fault",

and it pointed directly at my destructor for DataPiece, which simply calls "delete this" (even though I never actually call the destructor in my code, it must be an implicit call).

After briefly looking up this error, I primitively discovered that this generally occurs when attempting to illegally access a register in memory. So then I looked at how I initialized my DataPiece, realizing that I actually wasn't calling any of my constructors. So, I passed it a parameter 'this' to act as the QObject * parent, but this still didn't resolve my SIGSEGV issue.

Any thoughts?

Ok, thanks a lot! Marked as solved!