#366 closed defect (worksforme)

Using certain short file names crashes GTSS

Reported by: trnsz@… Owned by: Eric Swenson
Priority: major Milestone: MR12.9
Component: General Version: MR12.8
Keywords: Cc: Eric Swenson

Description

This is a very weird problem.

Oh GHM, in my home directory, attempting any I/O on certain file names will always crash, for example:

gtss, in >udd>Ring0>JJohnson:

GTSS 4JS3 (4.0)
*10 REM
*SAVE CRR03
DATA SAVED-CRR03
*SAVE CR03
DATA SAVED-CR03
*SAVE CR02

Error:  bad_area_format condition by gtss_mcfc_$open|1230
(>system_library_unbundled>bound_gcos_tss_)

CRR03 was fine, CR03 was fine, CR02 crashed.

new_proc, gtss again, trying to use these (existing) names as GTSS did create the CR02 file it crashed on:

*OLD CRR03
*OLD CR03
*OLD CR02

Error:  bad_area_format condition by gtss_mcfc_$open|1230
(>system_library_unbundled>bound_gcos_tss_)

Now, using a different directory:

new_proc
create_dir gtss
cwd gtss
gtss
GTSS 4JS3 (4.0)
*10 REM
*SAVE CRR03
DATA SAVED-CRR03
*SAVE CR03
DATA SAVED-CR03
*SAVE CR02
DATA SAVED-CR02
*OLD CRR03
*OLD CR03
*OLD CR02
*LIST

10 REM


*

As you can see above, the crash did not happen when using the new directory - it only happens in the home directory.

I have not investigated further.

Change History (2)

comment:1 by Eric Swenson, 11 months ago

I cannot reproduce this. This is what I get:

gtss
GTSS 4JS3 (4.0)
*10 rem
*save CRR03
DATA SAVED-CRR03
*SAVE CR03
DATA SAVED-CR03
*SAVE CR02
DATA SAVED-CR02
*

I don't get any bad_area_format condition.

comment:2 by Eric Swenson, 11 months ago

Resolution: worksforme
Status: newclosed
Note: See TracTickets for help on using tickets.