The debugger "solution" was not successful - which is logical given
that fact that nxagent does not crash. Thinko of mine.

Here's a way to reduce complexity a bit and possibly get a bit more output:
1. Instead of starting an x2go session run ssh -X to the server in two terminals
2. in the first ssh connection run "nxagent -ac :55" (55 is the one I
use normally, you can use any number here). An empty window should
appear
3. in the second ssh session run "xterm -display :55". The empty
window will now show you an frameless xterm
4. start the desktop environment by entering "startxfce4" into the
xterm. If that doesn't work try startlxde or just run a window
manager, e.g. "openbox &"
5. in the desktop environment run your application and try to provoke
the "crash"
6. post the end of nxagent's output from the first terminal

This way you will take libXcomp out of the equation (well, mostly). If
the crash happens I hope for some more output. If not, we can generate
a new nxagent with some debugging output enabled

Let me know the results,

Uli




On Wed, Feb 24, 2021 at 6:42 PM Joe <jsw140@hotmail.com> wrote:
>
>
> Feb 23, 2021 6:49:48 PM Ulrich Sibiller <uli42@gmx.de>:
>
> >
> > Feb 23, 2021 3:00:23 PM Ulrich Sibiller <uli42@gmx.de>:
> >
> >> On Tue, Feb 23, 2021 at 8:20 PM Joe W <jsw140@hotmail.com> wrote:
> >>>
> >>> I am using a program called Cliosoft SOS. It has a window that displays in columns like an Excel file. When I resize one of the columns then my X2GO session window crashes. The start window where I pick which session to start stays running.
> >>>
> >>> There is a horizontal scroll bar to move the columns sideways. When I drag that then the X2GO window crashes.
> >>
> >> Is that program available for testing?
> >
> > I don't know. I will ask them and I will also try your debugger suggestion.  The program requires quite a bit of setup before the columns are seen.
> >
> >>
> >>> I have attached the session log and the client debug console output showing a few of these crashes.
> >>
> >> The session log looks like a reconnect should be possible. Can you confirm?
> >>
> >
> > I can always reconnect after one of these crashes and see my desktop with ask the programs still running.  When I do then I see that my SOS columns have been resized.
> >
> >>> Is there some way to fix this or is it a bug that I should report?
> >>
> >> It is a bug - nx should not crash.
> >>
> >>> Is there any additional information that I should gather?
> >>
> >> Well, you could try the following:
> >> 1. start the session as always.
> >> 2. start an additional ssh session to the server as the same user or
> >> root to the server
> >> 3. run pgrep x2goagent and note the resulting PID (if you have
> >> multiple session running you will find multiple PIDs and need to
> >> identify the correct one)
> >> 4. attach the debugger to the PID: gdb -p PID
> >> 5. then try to provoke the crash. If it happens the debugger should
> >> kick in and show a prompt. Run the "bt" in command in the debugger and
> >> post the output you see.
> >>>
> >
> > I will try this in the next few days.
> >
> >>> Anything I should ask the software developer?
> >>
> >> Well, as written above a test version that triggers the problem would help.
> >>
> >> Uli
>
> I tried your debugger suggestion.
>
> The first time it told me to run debuginfo-install nxagent-3.5.99.25-4.el7.x86_64 so I did that.
>
> Each time after I attach the debugger then my x2go window is frozen so I cannot try changing anything.
>
> When I quit the debugger then the x2go window crashes.
>