The diagnostic on the last line should be:
Unexpected End of File at EOF
That's the memorable diagnostic from a CDC compiler.
brucee
On 6 November 2013 17:42, <6o205z...@sneakemail.com> wrote:
> I'm trying to create a plumbing rule so that I can right-click (in acme)
> on the diagnostic messa
I'm trying to create a plumbing rule so that I can right-click (in acme)
on the diagnostic messages produced by Python and get the file opened
with the appropriate line select. Unfortunately my attempts so far have
failed.
Question 1: Is there an easy way to "debug" plumbing rules (I'm using
On Tue Nov 5 13:06:06 EST 2013, cinap_len...@gmx.de wrote:
> how is this possible? execing a zero byte file should fail
> header parsing, which is portable code in sysexec(). can
> you reproduce the panic?
>
> i get this on a pc:
>
> term% ./xxx
> ./xxx: exec header invalid
this is not what hap
how is this possible? execing a zero byte file should fail
header parsing, which is portable code in sysexec(). can
you reproduce the panic?
i get this on a pc:
term% ./xxx
./xxx: exec header invalid
no panic...
--
cinap
i was running vl from /sys/src/cmd/vl/v.out, and got this
init: starting /bin/rc
ยต# panic: kmapfault: unmapped 0xe0198040
the clue is that v.out was 0 sized after the reboot. so it appears
that the panic is not correct. this should be a user fault.
- erik
