Comment 5 for bug 700194

What is really scary about yuor example is that gschem is so silent when loading the malicious code.

See the gsch2pcb-700194/-l,-m/one.sch example.

NOTHING is printed in the schem log, and it treats the schematic as if it were a blank file. (Which it otherwise is).

On the console we have:

Read garbage in [/home/pcjc2/gsch2pcb-700194/-l,-m/one.sch] :
>>
(display "Arbitrary code (1)\n")
<<

This would not be seen if running via xgsch2pcb, or loading the schematic from a copy of gschem started from a GUI environment.