SlickEdit Community

SlickEdit Product Discussion => SlickEdit® => Topic started by: rowbearto on November 01, 2021, 05:35:20 pm

Title: Issues in build window after manually sshing to build machine there
Post by: rowbearto on November 01, 2021, 05:35:20 pm
Look for se_build_window_issue.tgz in support and see the README file as well as the other files.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on November 02, 2021, 08:03:31 pm
Try turning on "Show VSLICKERRORPATH in build window" (Tools>Options>.Editing>General).  So far, all I can tell is that this is messing up the cursor location. I'm still looking into this.

Changing this option won't effect catting this log file. Your logfile already has output based on hiding the VSLICKERRORPATH.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on November 03, 2021, 01:31:29 am
I have found a bug that can occur if you hide certain build window lines like VSLICKERRORPATH. This will be fixed in 26.0.1. It's rare but your example is the perfect test case for it. Thanks

I'm not sure if this is the only problem you are hitting. After you turn on "Show VSLICKERRORPATH in the build window", post if you are still having any problems.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on November 03, 2021, 12:44:07 pm
Setting "Show VSLICKERRPATH in build window" seems to resolve the issue so far, haven't seen the issues again. I'll keep using this setting and see if anything new pops up.

Thanks!
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on November 08, 2021, 01:53:33 pm
It happened again this time with "Show VSLICKERRPATH" set to "ON".

Look for logbug.tgz on support. See the README file there for more information about the 2 different log files I provided.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on November 09, 2021, 01:06:03 pm
Still looking into this one. At the moment, it looks like it has something to do with processing of backspace under certain circumstances. You have a ton of backspaces in this test case.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on November 17, 2021, 04:01:11 am
Built new installer to fix this:

http://support.slickedit.com/outbound/2600/se_26000006_linux64.tar.gz (http://support.slickedit.com/outbound/2600/se_26000006_linux64.tar.gz)
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on November 17, 2021, 07:02:09 pm
Thanks Clark! Downloading now and will install it. I will let you know if there are still issues.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on November 17, 2021, 07:38:03 pm
Thanks again for the really good test case
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 06, 2021, 02:45:54 pm
It happened again even with the installer you provided.

Look for buildlog.tgz on support. See its README file.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on December 07, 2021, 06:01:46 pm
These problems are due to long lines messing up scrolling. I've fixed this for v26.0.1. Hard to say if there are any other problems going on but I can't reproduce any more problems with my fix.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 07, 2021, 06:28:25 pm
Are your fixes in 26.0.1 on top of what you provided in the special installer (post in this thread dated Nov 17)? There are more fixes besides that special installer?

If not then I'm also running with your same fixes yet the problem reproed.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on December 08, 2021, 01:50:11 am
The fixes you already have are merged into 26.0.1. You don't have the long line handling fix.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 14, 2021, 03:48:46 pm
I still see the issue in 26.0.1.

I uploaded to support see: buildlog-26.0.1.tar.gz
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on December 14, 2021, 10:44:15 pm
So far, I'm not able to reproduce these problems. There must be a very specific boundary condition occurring.

Are you able to reproduce this problem by doing this in the process buffer:

cat se_build.log
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 15, 2021, 02:16:58 pm
Unfortunately it doesn't happen when I do "cat se_build.log" :(

How to proceed?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on December 15, 2021, 03:14:13 pm
I'm going to try to come up with a way to record/play back what's going on the process buffer. Not sure if it's reasonably doable.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 15, 2021, 03:18:46 pm
Thanks!

When I do the real build it is slower than catting the build log, don't know if that means anything.

I also notice these <SOH> keep getting added 1 at a time during the real build when it happens.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 16, 2021, 06:07:18 pm
I was able to get rid of all the backspace characters in my log by setting TERM to xterm. It was defaulting to "dumb" before.

Even with this improvement to get rid of all the backspace characters I still did see this issue with <SOH> characters and my colored prompt not colored. I didn't save the log that time, will try to save it next time and see if it reproduces.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on December 17, 2021, 05:52:02 pm
I wasn't able to come up with a record/playback algorithm. Code is way too complicated. I put together a special installer with some good debug generation. Debug info is stored in user.cfg.xml. When you start SlickEdit, it clears the previous debug info. A ton of debug info is generated. It's best to start SlickEdit, run a test case that fails and exit.

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build_dbg.tar.gz (http://support.slickedit.com/outbound/2601/se_26000100_linux64_build_dbg.tar.gz)

Just run this debug version when you want to generated debug info for us to look at. Otherwise, run the normal 26.0.1 installer.

If you want, you can keep all those nasty backspaces if that helps reproduce a problem. It is possible there are still are multiple problems.

Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 18, 2021, 09:16:06 pm
Thanks. Trying it now.

I will try to reproduce with this debug load, it doesn't always happen.

EDIT: I see you wrote debug info is in user.cfg.xml
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on December 18, 2021, 09:45:14 pm
No luck reproing it so far today. But all I'm doing is retrying builds over and over. I think it happens when I'm using SlickEdit for other things while a build is ongoing. I won't be doing that again until I return from vacation next year - so I may not have the debug info until then.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on December 19, 2021, 12:26:30 am
This isn't as easy for you to reproduce as I thought. I suspect there's a specific timing involved to produce the right border condition.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 05, 2022, 07:34:19 pm
I was able to reproduce this with your debug version of SlickEdit. I saved the user.cfg.xml file, before/after closing SlickEdit. Hopefully it has the debug information you need.

Look for buildlogd.tar.gz on support.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 06, 2022, 08:15:34 pm
I have found a problem. Hopefully it is THE problem. SlickEdit maintains a bookmark for the process buffer so it knows where to insert text. This bookmark is supposed to track the line number (and column) which is used to scroll cursor positions for all windows viewing this buffer. This bookmark line number is getting messed up when a long line is inserted. When this happens, SlickEdit will no longer be able to properly scroll cursor positions. Hopefully, this is the last problem. In any case, there's no point in me looking for another bug until this one is fixed.

I'll post when I've a fix for this.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 06, 2022, 10:47:29 pm
Darn. There's a bug in the debug output. I need to output the line data differently. Otherwise, debugging your build output which has long lines is impossible.

I've built a new installer which fixes the debug generation.

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build2_dbg.tar.gz (http://support.slickedit.com/outbound/2601/se_26000100_linux64_build2_dbg.tar.gz)
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 07, 2022, 03:01:46 pm
I'm running the new debug version now. When the problem strikes again I will provide you the debug data.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 07, 2022, 03:58:56 pm
Happened again, this time with your latest debug installer.

It was too big for the support site, sent a download link to sstamp.

I had the Build(.process) window open when I did this build, not sure if that has anything to do with it or not? That window also didn't keep scrolling down, only showed the start of the build, while the build tool window did seem to scroll.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 08, 2022, 12:36:40 am
I'm seeing a \1 getting added in our xterm coloring function but I can't figure out why this is happening. It looks like a bug for sure. I've created another installer to give me more debug information in this function.

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build3_dbg.tar.gz (http://support.slickedit.com/outbound/2601/se_26000100_linux64_build3_dbg.tar.gz)

Please give this installer a try and reproduce this again.

Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 10, 2022, 09:49:02 pm
I reproduced it with your latest installer.

Look for buildlog4.tar.xz on support.

Notice I used xz compression to make it less than 50M so I could upload to support site.

To decompress it:

tar xvf buildlog4.tar.xz

My user.cfg.xml file is now 908MByte. How to make it smaller and get rid of old debug info?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 10, 2022, 10:06:26 pm
Go back to running the non debug version of SlickEdit. I’ll let you know what I find. Removing the debug requires manually editing user.cfg.xml and deleting the debug profile. Can’t remember the exact profile name.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 11, 2022, 07:06:29 pm
SlickEdit non-debug version seems very slow to me now, blocks often. Was wondering if it could be due to the large user.cfg.xml file with the debug info?

Would be interested in knowing how to remove all the debug info and see if this is the cause of my slowdowns?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 11, 2022, 07:13:14 pm
I just got rid of the <misc.build_debug> section of user.cfg.xml. It is now 295K instead of close to 1Gig.

Hopefully this blocking will go away...
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 11, 2022, 09:56:51 pm
Here is the first bug. Easy for me to locate because the <after_color_out_char1_not_here> element is generated only if there is a bug.

Code: [Select]
        47: -- ENABLE_...
        48:
]]>
</in_buffer>
<in_insert>
<![CDATA[-- Configuring done
]]>
</in_insert>
<before_color linenum="48" lineofs="0"/>
<before_color_in_pending_text/>
<before_color_in_mark linenum="49" lineofs="0"/>
<after_color_out_line linenum="94" lineofs="0"/>
<after_color_out_char1_not_here linenum="94" lineofs="0"/>
<after_color linenum="48" lineofs="0"/>
<before_scroll_mark linenum="49" lineofs="0"/>
<before_scroll_buffer>

Notice that this file has around 48 lines (probably 49 lines) coming into SlickEdit's xterm coloring function. I say around 48 lines because the <in_insert> text has been inserted already but there's not another buffer output element before the xterm coloring for us to see the exact buffer contents. Then after coloring we see <after_color_out_line linenum="94" lineofs="0"/>. This should be impossible. No way the build buffer has 94 lines. This is somehow related to this bug and why the \1 byte is not being removed.

I had to add a lot more debug into SlickEdit's xterm coloring function to further investigate this. Since this next xterm coloring function is generating a lot more debug, I've had to remove some other debug because this stuff is getting crazy large as you've noticed.

Here's installer #4:

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build4_dbg.tar.gz (http://support.slickedit.com/outbound/2601/se_26000100_linux64_build4_dbg.tar.gz)

I'm hoping that even if I can't quite understand what is going wrong this time, maybe I can do a mini playback and be able to trace the problem (assuming the problem isn't random). If I had to guess, it seems like the buffer being processed by the xterm color function is getting changed to  another buffer. If this is happening, I've got a lot more debug checking for this happening to narrow down where it's happening.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 12, 2022, 01:07:04 am
I will try it.

Maybe you would be able to reproduce this if you made a colored prompt like mine, you can extract it from my logfile, and make it a prompt using a bash shell in SE - set PS1 to it.

Then stay in this bash shell and do whatever builds you do (such as SlickEdit) in there, then you would repro it? Keep that as your shell with colored prompt, maybe you'll hit this issue like I do.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 12, 2022, 02:35:17 am
My builds are pretty simple. I don’t think a colored prompt would be enough. I do run sgrep in the build window all the time. It outputs a lot of color but I never have any problems.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 12, 2022, 02:39:08 am
Is there an easy way for you to generate the debug into a different file than user.cfg.xml?

Having the large user.cfg.xml slows down using SlickEdit significantly.

After I removed the debug I got a significant speedup in SlickEdit.

I don't know exactly when this issue may hit. I may need to use the debug SlickEdit for a while before it hits, and it will get slower and slower as user.cfg.xml gets bigger, and this will make it harder to use.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 12, 2022, 03:35:23 am
I’ll put something together. It will have to write the xml debug file on exit for performance and simplicity. The config system is a fancier cache.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 12, 2022, 02:52:32 pm
Here's installer #5:

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build5_dbg.tar.gz (http://support.slickedit.com/outbound/2601/se_26000100_linux64_build5_dbg.tar.gz)

Start up should be fast. Exit could be slow when writing a huge XML file.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 12, 2022, 03:10:27 pm
Thanks. Which xml file will have the debug information?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 12, 2022, 04:05:01 pm
build-debug.xml. Sorry, forgot to tell you.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 19, 2022, 02:25:29 pm
I captured the issue with debug installer #5.

Look for buildlog5.tar.xz on support.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 20, 2022, 02:16:12 pm
Thanks. I'm seeing the same problem but I've had to put in more debug closer to where the line number is somehow going weird. This installer will display a "say" debug message which pops up a window and tells you to send in your debug file when this bug occurs. You may not be seeing a bad prompt yet but that really doesn't matter. That's just an additional bad side effect.

Here's installer #6:

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build6_dbg.tar.gz (http://support.slickedit.com/outbound/2601/se_26000100_linux64_build6_dbg.tar.gz)

Sorry this is taking so long. The code doesn't look very complicated but I can't explain/understand why the line number just suddenly goes wonky. The previous debug was around code that was more complicated that I thought would be more likely to be the cause of the line number going wonky. This time, I've put debug in earlier around pretty much every simple statement. The debug info indicates that the file is not getting switched out which could have explained the sudden wonky line number.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on January 21, 2022, 09:53:45 pm
Not sure if I caught it or not, but look for buildlog.tar.xz on support.

The debug version went haywire, there was a stack which you can see in the stack.log.

I figured I'd capture the debug output, but not sure any real problem in there.

I have noticed occasionally that the debug version runs out of memory and I have to restart it. That may have happened here, I'm not sure.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on January 21, 2022, 10:07:18 pm
The bug I'm looking for didn't happen here.  Search for "after_color_out_char1_not_here" in build-debug.xml. That's what I'm looking for. This latest installer is supposed to display a "say" debug window when that element is output. You may just be having problems due to running out of memory. You may need to restart to avoid running out of memory.

I did make a fix in this last build. However, the fix I made had to do with how backspace is handled and in the last debug file, there weren't any backspace characters.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on February 02, 2022, 09:58:08 pm
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? 
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on February 02, 2022, 10:09:47 pm
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.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on February 03, 2022, 02:09:28 am
Here's installer #7:

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build_fix_2022_02_02.tar.gz (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.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on February 03, 2022, 02:19:59 pm
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.

Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on February 07, 2022, 07:31:57 pm
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.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on February 07, 2022, 07:38:39 pm
Ok. Switching back to the previous installer (#6) will provide the debug I need.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on April 01, 2022, 02:00:05 pm
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?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on April 01, 2022, 03:52:03 pm
Only difference is no debug generation. I’ll double check.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on April 04, 2022, 04:41:47 pm
I readded the debug.

Here's installer #8:

http://support.slickedit.com/outbound/2601/se_26000100_linux64_build8_dbg.tar.gz (http://support.slickedit.com/outbound/2601/se_26000100_linux64_build8_dbg.tar.gz)
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on April 13, 2022, 06:20:32 pm
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.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on April 13, 2022, 06:48:43 pm
The debug must change the timing. It’s just generating xml data in memory which should be fast.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on May 20, 2022, 02:06:59 pm
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.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on June 03, 2022, 02:17:55 pm
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?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on June 03, 2022, 02:56:47 pm
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.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on June 03, 2022, 03:20:11 pm
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?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on June 03, 2022, 03:29:32 pm
FYI I'm using Patrick's commit:  https://community.slickedit.com/index.php/topic,18828.msg74731.html#msg74731 which has build date May 9, 2022.

I'm also using Qt5 version.

Maybe something with this commit makes it happen more?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on June 03, 2022, 03:58:40 pm
It’s just a timing dependent problem.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on June 03, 2022, 11:40:20 pm
Here's a new Qt5 installer of 26.0.2 with debug and the mods I thought of.

http://support.slickedit.com/outbound/2602/se_26000201_linux64qt5-2022-06-03.tar.gz (http://support.slickedit.com/outbound/2602/se_26000201_linux64qt5-2022-06-03.tar.gz)

Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on June 04, 2022, 02:43:19 pm
Thanks so much Clark! I will try it out.

Will it still fill up memory and I have to eventually exit it because consuming too much memory?

Or did you take care of that? You mentioned truncating the data in a previous post.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on June 04, 2022, 02:56:05 pm
There is truncation in this one. If memory gets too large let me know and I’ll truncate it more. I shouldn’t need that much history as long as you exit when you get a debug message telling you to exit because a bug was found.
Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on June 04, 2022, 11:11:55 pm
After firing it up and doing a few builds it crashed during a next build.

Look for crash_2022_06.tar.xz on support for the core dump file and user.cfg.xml
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on June 05, 2022, 12:53:17 pm
Messed up on truncation. Try this Qt5 installer of 26.0.2:

http://support.slickedit.com/outbound/2602/se_26000201_linux64qt5-2022-06-05.tar.gz (http://support.slickedit.com/outbound/2602/se_26000201_linux64qt5-2022-06-05.tar.gz)

This installer has more truncation.

Title: Re: Issues in build window after manually sshing to build machine there
Post by: rowbearto on June 07, 2022, 03:21:14 pm
Unfortunately it is not reproducing :( Did you add something else besides debug, or only debug?
Title: Re: Issues in build window after manually sshing to build machine there
Post by: Clark on June 07, 2022, 06:17:47 pm
Besides debug, there is an additional fix but this fix was also in the build that Patrick made for you for Python.