#1287 TclPro interpreters fail in I18N directory: "Can't find a u

obsolete: 8.1
closed-invalid
Don Porter
5
2001-09-12
2000-10-26
Anonymous
No

OriginalBugID: 2094 Bug
Version: 1.3b1
SubmitDate: '1999-05-18'
LastModified: '1999-05-18'
Severity: SER
Status: UnAssn
Submitter: foster
ChangedBy: foster
OS: All Windows
OSVersion: NA
Machine: NA
FixedDate: '2000-10-25'
FixedInVersion: NA
ClosedDate: '2000-10-25'

After installing TclPro 1.3 in a directory path called "C:/tests/abcdefgh?", trying to
run either protclsh81.exe or prowish81.exe fails with an error messages such as:
----------------------------------------------------------------
Fatal Error in Wish:
Can't find a usable init.tcl in the following directories:
C:/tests/abcdefgh○/TclPro1.3b1/win32-ix86/lib/tcl8.1
C:/tests/abcdefgh?/TclPro1.3b1/win32-ix86/lib/tcl8.1
C:/tests/abcdefgh?/TclPro1.3b1/lib/tcl8.1
C:/tests/abcdefgh?/TclPro1.3b1/lib/tcl8.1/library
C:/tests/abcdefgh?/TclPro1.3b1/library C:/tests/abcdefgh/TclPro1.3b1/../tcl8.1/library
C:/tests/abcdefgh?/../tcl8.1/library
This probably means that Tcl wasn't installed properly.
------------------------------------------

Notes:
1. All three special characters ( ? ) must occur in sequence, using any subset will not fail.
2. The special characters are (un)encoded badly only in the first directory name in the search
list, and if they were handled correctly would match the second directory in the list.
3. The actual init.tcl file is located in the third directory listed (.../lib/tcl8.1)
4. After the error report, protclsh.exe behaves gracefully, but prowish.exe bombs out with:
Exception: hardcoded breakpoint (0x80000003), Address (0x004014ec)
(I'll open a separate bug for wish's unrefined behavior when it can't find init.tcl)
5. As an alternative to copying and pasting the special directory name directly from the bug report,
the three special characters can each be generated directly from the Windows keyboard by
holding down the ALT key while entering each character's 4-digit code on the numeric keypad:
ALT-0239 ALT-0191 ALT-0174

05/18/1999 14:28 - foster - Scott & Scott suspect the wrapper-related startup code in pro*sh.
Note also that this problem does *not* occur with plain Tcl interps (tclsh, wish)

Discussion

  • Don Porter
    Don Porter
    2001-04-05

    • labels: 104244 --> 38. Init - Library - Autoload
    • summary: TclPro interpreters fail in I18N directory: "Can't find a u --> TclPro interpreters fail in I18N directory: "Can't find a u
     
    • summary: TclPro interpreters fail in I18N directory: "Can't find a u --> TclPro interpreters fail in I18N directory: "Can't find a u
    • assigned_to: nobody --> dgp
     
  • Don Porter
    Don Porter
    2001-09-10

    • summary: TclPro interpreters fail in I18N directory: "Can't find a u --> TclPro interpreters fail in I18N directory: "Can't find a u
     
  • Don Porter
    Don Porter
    2001-09-10

    Logged In: YES
    user_id=80530

    According to the imported comment, this occurs only
    in TclPro, not Tcl. I'm inclined to close it as
    Invalid, since I don't know of any way to transfer
    it to the TclPro project.

    Unless I hear dissent in a few days, I'll close this.

     
  • Don Porter
    Don Porter
    2001-09-12

    Logged In: YES
    user_id=80530

    This reports a problem with TclPro, not Tcl. Re-file
    it with the TclPro project if it is still valid.

     
  • Don Porter
    Don Porter
    2001-09-12

    • summary: TclPro interpreters fail in I18N directory: "Can't find a u --> TclPro interpreters fail in I18N directory: "Can't find a u
    • status: open --> closed-invalid