ECHOed TRACE of TCP client port OPEN on Linux appears corrupted

[Siskin-Bot]

Submitted by: kcollins

I ran the example code shown below using both the Windows a94 build and the Linux a94 build. I diffed the ECHO output and found numerous differences in the output, such as:

12c12
<           4: url? : action! [value]

---
>           4: urle : action! [value]

20c20
<           4: spec : tcp://localhost:9999

---
>           4: spct : tcp://localhost:9999

Could this be caused by a memory corruption bug in the Linux open native?

REBOL [
]

secure [debug allow]
trace on

wait 1
echo to-file now/time

open tcp://localhost:9999

---

^{Imported from: CureCode [ Version: alpha 94 Type: Bug Platform: Linux x86 libc6 Category: Ports Reproduce: Always Fixed-in:none ]
Imported from: metaeducation#1322}

Comments:

---

Rebolbot added the Type.bug on Jan 12, 2016

---

[Oldes]

Confirmed with shorter code:

trace on
open tcp://localhost:9999

On Linux I see:

>> open tcp://localhost:9999
 1: open : action! [
 2: tcp://localhost:9999
    --> open
         1: case : native! [
         2: [
            --> case
             1: file? : action! [
             2: spio : tcp://localhost:9999
                --> file?
            <-- file? == false
             4: urle : action! [
             5: spio : tcp://localhost:9999

while on Windows it's:

             4: url? : action! [
             5: spec : tcp://localhost:9999

[Oldes]

The corruption was visible in other traces... for example when used:

trace on find-min [1 2 3]

In the output there was:

...
   14: [if lesser? first series first spot [spot: series]
      --> forskip
       1: if : native! [condition true-branch /only]
       2: lesser? : native! [value1 value2]
       3: first : native! [value]
       4: serve! : [1 2 3]
...

Where it actually should be:

       4: series : [1 2 3]