Issues in build window after manually sshing to build machine there

[Clark]

Prior to the latest build with the fix I put in, you were able to get this "after_color_out_char1_not_here" bug to happen fairly easily. Now, you haven't been able to make this happen. Is this an accurate assessment? 

[rowbearto]

Yes I have not been able to reproduce the issue. I don't see your "say" statement or the <SOH> with your debug load. I have done many builds I would have expected to see it by now.

[Clark]

Here's installer #7:

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build_fix_2022_02_02.tar.gz

This installer has no debug in it but has the same fix that was in the last debug installer. The latest hot fixes are rolled into this installer. That just means you don't need to install the latest hot fix build unless it occurs after the date this installer was built.

[rowbearto]

Thanks. I will go ahead and use installer #7. I stopped using the debug load because it would run out of memory. Sounds like installer #7 won't run out of memory since debug is removed.

I didn't notice there was a hotfix for 26.0.1. I usually get a message about new hotfixes because I am subscribed to:

https://community.slickedit.com/index.php/topic,6567.0.html

But looks like that thread was not updated when new hotfix was available.

[rowbearto]

I just got some of the <SOH> or \1 with the installer #7. So looks like the issue is still there. I changed which build I'm doing today. I will go back to using your last debug load see if I can catch it.

[Clark]

Ok. Switching back to the previous installer (#6) will provide the debug I need.

[rowbearto]

Unfortunately for the past few weeks I haven't done much coding. But with a few days of usage it seems that the issue does not reproduce with the debug installer (#6), but it does reproduce with installer #7.

Furthermore using installer #7 I observed it happening even without sshing into my build machine and using the default se shell.

I think something in installer #6 is preventing the problem from occurring. Maybe another debug installer is needed to track this down?

[Clark]

Only difference is no debug generation. I’ll double check.

[Clark]

I readded the debug.

Here's installer #8:

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build8_dbg.tar.gz

[rowbearto]

It doesn't repro with installer #8, but it does repro with installer #7.

I think whatever debug you added between installer #5 and #6 is causing the issue to not occur.

[Clark]

The debug must change the timing. It’s just generating xml data in memory which should be fast.

[rowbearto]

FYI: Still seeing this issue in 26.0.2 with Patrick's commit in: https://community.slickedit.com/index.php/topic,18828.msg74731.html#msg74731 which has build date May 9, 2022.

[rowbearto]

It is happening quite often, kind of annoying. When I want to manually enter a command I have to manually remove the <SOH>. It happens without sshing in first (although my build script does do ssh).

Is there another way to add debug that could not make the problem go away?

[Clark]

How about I build an installer that generates the debug BUT doesn't write the data out unless a problem is detected? In addition, the data will need to truncated from time to time since the data generated can be very large.

I'm guessing the debug data changes the timing and this bug is DEFINITELY dependent on timing. It could be a compiler code generation bug but I haven't seen one of those in a very long time.

[rowbearto]

OK. I thought I remembered from a past post that you were writing xml (to a file?) when bug is detected and that changes the timing? Maybe just save a few global variables when bug is detected to not change the timing much? Then write the xml later? Maybe this is already what you are proposing?