Hi Uli,
Try to debug the code using the debugger? Adding print lines is not the way to
do it.
I hope somebody can say how to re-compile the code with debug symbols and if
gdb is good enough?
Kind regards,
Melroy van den Berg
‐‐‐ Original Message ‐‐‐
Op woensdag, mei 20, 2020 2:16 PM,
On Wed, May 20, 2020 at 5:08 PM Melroy van den Berg
wrote:
> Try to debug the code using the debugger? Adding print lines is not the way
> to do it.
"the debugger" is something I don't know. I am not developing software
on Windows (I am not even using Windows if I can avoid it). Therefore
I
Running with --libssh-packetlog shows a bit more:
[2020/05/20 14:08:36.287745, 2] ssh_socket_connect: Nonblocking
connection socket: 2228
[2020/05/20 14:08:36.287745, 2] ssh_connect: Socket connecting, now
waiting for the callbacks to work
[2020/05/20 14:08:36.288743, 3] ssh_connect: Actual
Running with --libssh-debug does not provide any further hint:
x2go-DEBUG-../src/sshmasterconnection.cpp:805> Session port after
config file parse: 22
[2020/05/20 13:49:23.492000, 2] ssh_connect: libssh 0.9.3 (c)
2003-2019 Aris Adamantiadis, Andreas Schneider and libssh
contributors. Distributed
Here's the output of the centos7 nightly build
x2goclient-4.1.2.3-0.0x2go1.0.git20200520.1947.heuler.el7.x86_64 which
is working with the same session setup:
x2go-DEBUG-../src/sshmasterconnection.cpp:795> Session port before
config file parse: 22
x2go-DEBUG-../src/sshmasterconnection.cpp:805>
Hi,
both x2goclient for windows 4.1.2.2-20200213 and
https://code.x2go.org/releases/binary-win32/x2goclient/heuler/mingw32-4.8/qt-4.8/x2goclient-4.1.2.3-2020.05.20-a1a2f62-setup.exe
are crashing during connection establishment when using a proxy
(output from the debug build):
