Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

trace incompatibility in 8.4 and 8.3 ?

6 views
Skip to first unread message

Mary Lei

unread,
May 30, 2006, 2:24:43 PM5/30/06
to
We recently upgraded from old tcl 8.3.5 to
8.4.12.
A lot of our code depends on
setting trace to resume processing.
We noticed that sometimes trace proc
is not invoked in 8.4 but works
perfectly fine in 8.3.

Has anyone noticed this issue ?

Don Porter

unread,
May 30, 2006, 4:02:59 PM5/30/06
to

That's not nearly enough information. Got a small example of something
that works for you in 8.3.5 and not in 8.4.13 ?

--
| Don Porter Mathematical and Computational Sciences Division |
| donald...@nist.gov Information Technology Laboratory |
| http://math.nist.gov/~DPorter/ NIST |
|______________________________________________________________________|

Mary Lei

unread,
May 30, 2006, 6:51:25 PM5/30/06
to d...@nist.gov
Don Porter wrote:
> Mary Lei wrote:
>
>>We recently upgraded from old tcl 8.3.5 to
>>8.4.12.
>>A lot of our code depends on
>>setting trace to resume processing.
>>We noticed that sometimes trace proc
>>is not invoked in 8.4 but works
>>perfectly fine in 8.3.
>>
>>Has anyone noticed this issue ?
>
>
> That's not nearly enough information. Got a small example of something
> that works for you in 8.3.5 and not in 8.4.13 ?
>
It is difficult to generate a small example since
this issue occurs under load and does not occur every time.

I updated some code to the new trace syntax
and was able to get things flowing again.
So I suspect trace incompatibility of 8.4 with 8.3.

Don Porter

unread,
May 30, 2006, 11:42:39 PM5/30/06
to
Don Porter wrote:
>> That's not nearly enough information. Got a small example of something
>> that works for you in 8.3.5 and not in 8.4.13 ?

Mary Lei wrote:
> It is difficult to generate a small example since
> this issue occurs under load and does not occur every time.

...


> So I suspect trace incompatibility of 8.4 with 8.3.

You can suspect whatever you like, but without a clear report
of an identifiable problem, nothing's going to be done about something
that may not exist or may be user error.

Doesn't help that the hint of a possible problem comes years beyond
8.3's end of life when all the action has moved to 8.5 development.

0 new messages