Editor Crashes

Brought to you by: rexx

#223 Editor Crashes

Milestone: Next Release

Status: pending-fixed

Owner: Mark Hessling

Labels: None

Priority: 8

Updated: 2013-06-21

Created: 2011-09-07

Creator: clickclick

Private: No

I have been wanting to report this ever since 3.2, but now that 3.3 rc1 is still broken, I will report my problem here.

To recreate the crash, do the following:

Take the attached text file and enter all/(I) at the command line. Page up and down and everything is fine. Go to the bottom and use the up-arrow key and keep it pressed until you reach the top. A -(dash) will appear in the 1st prefix line on the left and after that the editor will crash . Both theg and thec have this problem. I have a user.dmp if you need it,

Discussion

clickclick - 2011-09-07

Windows Update List

$Win7MU.txt

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-07

priority: 5 --> 8
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-07

DrWatson log file

drwtsn32.log

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-07

Crash Dump

user.dmp

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-07

My Profile

profile.the

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

LesK - 2011-09-07

I can't make 3.3b3 or RC2 crash, so maybe it's fixed. Did you make 3.3b3 crash?

Les

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-07

Yes, 3.3b3 was the last version I used before trying RC1. Where did you find RC2?

I don't see it.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-07

I forgot to mention that I am using XP/SP3 + all post security fixes.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2011-09-08

Crashes on Win7 SP1 too.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

LesK - 2011-09-08

I replicated the crash on W7 when I used your profile.the. Had a dickens of a time figuring out where you had moved the ENTER key to!

I'd guess the bug has something to do with KEDIT KEDIT KEDIT mode. I didn't see the bug before because I use XEDIT XEDIT XEDIT mode.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-08

I just can't get away from the old 3270 feel of things. :-)

Thanks for verifying. I tried XEDIT mode, but if I page to the bottom and try to use the arrow-keys,
I do not get the scrolling effect to get back to the top. I have to use page-up, so I am unable to create
the same scenario as with KEDIT mode

I ended up with Kedit on my earlier DOS machines and basically stuck with that as an Xedit replacement for
the PC. Sometime later, I found out about THE and did not bother switching to Xedit mode.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-08

If you use compat XEDIT XEDIT KEDIT/THE, you will still get the crash. Looks like a problem in the way the arrow-key is processed when it gets to the top.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

LesK - 2011-09-08

It appears that it's more than just the definition of CURU. I defined it in XEDIT mode as just CURSOR UP (was CURSOR SCREEN UP) and did not get the crash on W7 or XP. The last COMPAT setting is supposed to be for function keys, so I don't see the correlation to the crash. I would expect the 2nd setting (feel) to be the controlling one!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-08

I can get THE to crash in XEDIT mode too with the following in my profile:
compat xedit xedit xedit
SET AUTOSCROLL 1
DEF CURU CURSOR UP
DEF CURU CURSOR DOWN

Now, I can scroll up and down with the arrow keys in xedit mode like the other modes, but THE will still crash if you scroll up in a file that is displaying shadow lines. This seems to be the common denominator for the crash to occur. If you turn shadow off - no problems scrolling up. Scrolling down doesn't have this problem

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2011-09-09

ooops. there's a typo. Shuld be

DEF CURD CURSOR DOWN

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mark Hessling - 2011-09-11

assigned_to: nobody --> rexx

status: open --> pending-fixed
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mark Hessling - 2011-09-11

The principle circumstances of the bug are to have CURLINE ON 2, and the first line(s) of the file are shadow lines and SHADOW ON and scrolling up a line.
Bug has been fixed!

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

clickclick - 2011-09-11

Thanks Mark for taking the time to look into this. I appreciate it.

Al

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Nobody/Anonymous - 2011-12-29

Is there a newer version of this application that has the crash fix in it already?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Mark Hessling - 2013-06-21

Group: --> Next Release
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.