At 06:39 PM 1/7/2002 +0000, Simon Glover wrote:
> Currently, whenever we create a new string with a call to string_make,
> we allocate the memory for it by a simple call to malloc (via
> mem_sys_allocate in memory.c). However, we don't check the return value
> of this call, so if the malloc fails, Parrot promptly segfaults
> when we try to make the string null-terminated. For example,
> the code
>
> set S0, "a"
> repeat S0, S0, 2000000000
> end
>
> invariably causes Parrot to segfault on my machine. What's the best way
> to fix this?
repeat needs to throw an exception. I need to get exception handling
defined for the engine. It's on the todo list--I'll move it up.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
