Author Topic: Issues in build window after manually sshing to build machine there  (Read 7481 times)

rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #15 on: December 15, 2021, 02:16:58 pm »
Unfortunately it doesn't happen when I do "cat se_build.log" :(

How to proceed?

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6433
  • Hero Points: 501
Re: Issues in build window after manually sshing to build machine there
« Reply #16 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.

rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #17 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.

rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #18 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.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6433
  • Hero Points: 501
Re: Issues in build window after manually sshing to build machine there
« Reply #19 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

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.


rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #20 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
« Last Edit: December 18, 2021, 09:19:31 pm by rowbearto »

rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #21 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.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6433
  • Hero Points: 501
Re: Issues in build window after manually sshing to build machine there
« Reply #22 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.

rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #23 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.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6433
  • Hero Points: 501
Re: Issues in build window after manually sshing to build machine there
« Reply #24 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.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6433
  • Hero Points: 501
Re: Issues in build window after manually sshing to build machine there
« Reply #25 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

rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #26 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.

rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #27 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.

Clark

  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 6433
  • Hero Points: 501
Re: Issues in build window after manually sshing to build machine there
« Reply #28 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

Please give this installer a try and reproduce this again.


rowbearto

  • Senior Community Member
  • Posts: 2222
  • Hero Points: 132
Re: Issues in build window after manually sshing to build machine there
« Reply #29 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?