This rather dodgy bit of code
.sub main
$S0 = read $P1, 1
end
.end
Causes a crash, instead of raising an exception.
Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
Thread 0 Crashed:
#0 0x00024808 in PIO_read (io.c:911)
#1 0x0004b188 in Parrot_read_s_p_ic (core_ops.c:369)
#2 0x00111ddc in runops_slow_core (runops_cores.c:146)
#3 0x0000aa10 in runops_int (interpreter.c:838)
#4 0x0000aad8 in runops_ex (interpreter.c:865)
#5 0x0000ad04 in runops (interpreter.c:941)
#6 0x0000ea20 in Parrot_runcode (embed.c:693)
#7 0x0000378c in main (main.c:559)
#8 0x00001d60 in _start (crt.c:267)
#9 0x00001be0 in start
Thread 1:
#0 0x9003e9a8 in semaphore_wait_signal_trap
#1 0x9003e7c4 in _pthread_cond_wait
#2 0x0019a988 in queue_wait (tsq.c:319)
#3 0x00108c24 in event_thread (events.c:905)
#4 0x90020c28 in _pthread_body
Thread 2:
#0 0x9002568c in select
#1 0x001085a0 in io_thread (events.c:647)
#2 0x90020c28 in _pthread_body
--
Will "Coke" Coleda will at coleda
dot com
> .sub main
> $S0 = read $P1, 1
> end
> .end
> Causes a crash, instead of raising an exception.
as probably any other IO opcode. Proper error handling for IO is much
work and a lot of fun.
Patches welcome.
leo
> > Causes a crash, instead of raising an exception.
>
> as probably any other IO opcode. Proper error handling for IO is much
> work and a lot of fun.
>
> Patches welcome.
These were things I wanted to do quite a while ago, but then I got a
new job, moved too a new town, had no connection to the internet. At
the moment I work through a huge backlog of mails and try to get
familar with the recent changes of the code. So don't hold your
breath.
bye
boe
--
Juergen Boemmels boem...@physik.uni-kl.de
Fachbereich Physik Tel: ++49-(0)631-205-2817
Universitaet Kaiserslautern Fax: ++49-(0)631-205-3906
PGP Key fingerprint = 9F 56 54 3D 45 C1 32 6F 23 F6 C7 2F 85 93 DD 47