• ~negating strings (turned out it had already been filed and fixed in a pre-release bug 1
• blessed object lost in anon sub from 'C' call 20010116.003 (local)
• PL_origfilename not updated properly in error messages 3 (not filed)
• perlcall(1) examples don't work with perl 5.6.0 with threads 20010116.015 (local)
• my $var = val if (..) doesn't work properly 20010309.009 (local)
• <> vs <STDIN> is OS specific 20010925.051 (local - found with Andrew Allen)
• seek doesn't work in an >> append 20011011.020 (local)
• Solaris regex loses (\d) match 9 (not filed)
• syntax error causes segfault 29161 (local)
• push returning total number elements instead of number new elements 37186 (local)
• "in memory" files don't call STORE method when tied 43789 (local)
• panic: top_env from embedded perl using 'do' with unused XS calls 44051 (local)
• setting $0 in embedded eval_pv causes segfault 44129 (local)
• illegal division by zero in short-circuit expr still triggered (local)
• IO::Select can_read() without timeout hangs whereas can_read(<timeout>) works (local)
• Perl Getopt::Long options are not boolean testable (and why I hate unnecessary libraries)

• Bug #18780 (local) is a problem with the C API version of eval() getting the wrong receiver in it's scope binding.
• Bug #20858 (local) multiple parallel assignments are inconsistent

cat some_file | xargs -i -l1 echo START {} END
cat some_file | xargs -l1 -i echo START {} END

I then found a similar but much messier spreadsheet bug. If a column with mixed types is in the query selection but not actually used by the "select" then we can get corrupted results for the select. The issue in the screenshot is because our 'query' uses '$A$2:$D$11' and can be fixed by reducing that span, but that doesn't help if the unused column is in between the other two. Here's two screenshots (1, 2) and the xlsx spreadsheet you can import

1. [6.2g] missed expression for '==',
2. [6.2g] coverage on/off pragmas intermittently cover enclosed instantiations
3. [6.3c] Simulation ending before coverage database is written

1. Pointer crash: [Fixed in 6.3c] Examine large source in GUI, turn on source annotation, run so that PLI does tf_dostop, GUI suddenly crashes and outputs: "Bad pointer access... Closing vish."
2. [6.3c] vcover merge bug: Intermittent failure:
   File 'new.ucdb' does not match code/functional coverage type of previous file(s)
   [[Design was not altered/recompiled between runs]]
3. [6.3c] vcover merge bug: 50% Intermittent failure:
   "(vlib-5) ****** Memory failure. ***** Bad pointer/access type passed to memory subsystem. Pointer may have been previously deallocated.(vlib-5) ****** Memory failure. *****"
   And then vcover runs indefinitely, sucking up system resources until it is killed.
4. [6.3c] vcover merge disappearing error:
   Multiple test data records with the same name encountered during the merge of file 'new.ucdb'. These test data records contain conflicting data. For more details, rerun merge with the '-verbose' option set.
   Amusingly, when I run with -verbose, the error disappears.
5. [6.3c] vcover mis-parsing signal names with verilog "\escaped identifiers ;"