Having a weird issue with PGDac and securebridge on Linux with Lazarus

[snorkel]

I have a app that uses SecureBridge to connect to a SSH
server and then opens a tunnel for the PGdac connection to use.
This works fine on Windows with Lazarus, on Linux (Latest ArchLinux I686 32bit) it also works,
but not in the IDE, when I run it from the IDE the PGDac connection fails with a error code 4 system call interrupted. If I run the exe directly it works fine.

Anyone have any ideas?

[snorkel]

oh, forgot to add I am running the latest stable lazarus with compiler 2.6.2
along with latest versions of PGDac and Securebridge.

Actual Error is:

Error on data reading from the connection:
Interrupted system call.
Socket Error Code 4($4)

I thought it might because of the xserver conflicting with threads or something, so I had the
application output to another X display and still got the same error.

Again the app works fine when run outside the IDE, I just cant get past the PGDac connect in the IDE right after the tunnel channel in Sbridge is connected.

[AlexP]

Hello,

We haven't yet tested our products on the latest versions of FPC and Lazarus, there was no such problem on the previous versions. We will check this behaviour and inform you about the results.

[snorkel]

ok, thanks.
Just a FYI, it was doing it on Lazarus 1.0.6 and the 2.6.0 compiler as well.
I just updated to the 2.6.2 compiler yesterday.

[snorkel]

I will try and make a simple Lazarus project that reproduces the issue.

[snorkel]

Just a FYI, I sent a support request ticket with this issue and a example Lazarus project
as a zip file.

[snorkel]

Also just a FYI, this only happens on Linux.
Works great on lazarus win32 in the IDE even with latest lazarus 1.0.6 and FPC 2.6.2 which was just released as stable a few days ago.

[snorkel]

Also as a FYI,
I did have the my test apps display go to a different X session to eliminate any IDE thread locking issues and the same error appears, so it's not related to threads and the IDE.

[DemetrionQ]

Hello.

Thank you for the information, we have reproduced the problem and been investigating it.

[snorkel]

Have you guys found anything out about this yet?

[DemetrionQ]

Hello.

We haven't solved this problem yet. We will inform you as soon as we fix it.

[snorkel]

Any updates on this?

[DemetrionQ]

Hello.

This is a SecureBridge problem. We will fix it in the next SecureBridge build.