Known Bugs in TclPro 1.4

This page lists the known bugs for TclPro 1.4 and supported extensions. If you have found a bug that is not listed on this page or explained in the FAQ, please send us a bug report.

Known Bugs Index

1. TclPro 1.4

1.1. Invoking prodebug, procheck, procomp, prowrap or prolicense on Linux may generate a core file.

2. TclPro 1.4 wrapper

2.1. 'package require registry' (or dde) fails when wrapped and run on windows.

3. TclPro 1.4 debugger

3.1. can't extend cases within a switch.

1. TclPro 1.4

1.1. Invoking prodebug, procheck, procomp, prowrap or prolicense on Linux may generate a core file.

Bug 979
Note this applies to Linux only.
Prodebug, procheck, procomp, prowrap, and prolicense are shell scripts which set environment variables and invoke the binary for the corresponding tools. If the environment variables SHLIB_PATH and LD_LIBRARY_PATH are not set when executing these scripts, a core file may generated. This bug does not affect the functionality of TclPro tools. The resulting core file can be deleted.

Work Around:

Set both the LD_LIBRARY_PATH and SHLIB_PATH environment variables. The following is an example of how to do so in the "sh" shell:

	LD_LIBRARY_PATH="/opt/ajuba/TclPro1.4/lib"
	SHLIB_PATH="/opt/ajuba/TclPro1.4/lib"

2. TclPro 1.4 wrapper

2.1. 'package require registry' (or dde) fails when wrapped and run on windows.

Bug 6278
Wrapping is successfull, but running fails. /lib/prowrapuses/prowrapUses.tcl doesn't reroute package require calls for the registry and dde extensions on windows.
The work-around in the client script is:

  if {[info exist tcl_platform(isWrapped)]} {
      load {} Dde
      load {} Registry
  } else {
      package require dde
      package require registry
  }

3. TclPro 1.4 debugger

3.1. can't extend cases within a switch.

Bug 6279
The following script can not be loaded into the debugger.

  set a "one"
  switch $a {
      "one" \ 
      {
          puts "was one"
      }
      default \ 
      {
          puts "not one"
      }
  }

The instrumenting parser on top of the core (in the debugger) can't parse the above even though the switch command doesn't have a problem with it when sourced into the shell. It is considered legal even though this convention doesn't follow the TclStyleGuide.

The current work-around is not to extend the line of a case to put the open curly on the second line.