Unhandled signal

[Brian T. Rice]

Follow-up:

There's nothing wrong with the VM or image in this case (in case anyone 
was wondering). After a conversation on the IRC channel, it was revealed 
that John was attempting a resend for which a further method had not 
been written. There is no handler for notFoundOn:after:, and this is the 
cause of the problem. It will be added now.

Thanks.

Brian T. Rice wrote:
> This is a bit misleading. It's a result in the VM of trying to raise an 
> condition using a message-send and failing (in the special objects 
> array). Here's the code:
> 
> i@(Interpreter pointer) signal: signalIndex on: args arity: n
> "Invokes a 'signal': a selector known in the SpecialObjectsArray so that
> errors in primitives can issue Conditions."
> [| args!(ObjectPointer pointer) selector!ObjectPointer 
> def!(MethodDefinition pointer) method!(CompiledMethod pointer) |
>    selector: (CurrentMemory specialAt: signalIndex).
>    def: (selector dispatchTo: args arity: n above: 0).
>    def
>      ifNil: [error: 'Unhandled signal.'].
>    method: def method pointer!(CompiledMethod pointer) cast.
>    i apply: method to: args arity: n withOptionals: Nil
> ] export.
> 
> Basically, if it looks up this signalling selector and doesn't find a 
> method, the VM dies with this message. Unfortunately, you can't tell 
> what the message was yet. :/
> 
> Lendvai Attila wrote:
> 
>> :: How should I go about debugging an unhandled signal? Is the :: vm 
>> catching a segfault here?
>> :: :: I see the following message from the bootstrapped VM when :: 
>> running some of my own code.
>> :: :: Slate: Unhandled signal.
>>
>> this is a unhandled Slate Condition... probably some more info will be
>> written once the vm gets more grown up.
>>
>> - 101
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: water.vcf
Type: text/x-vcard
Size: 208 bytes
Desc: not available
Url : /archives/slate/attachments/20040731/214ad2b1/water.vcf