From: matz@... (Yukihiro Matsumoto) Date: 2004-05-22T11:14:54+09:00 Subject: Re: [PATCH] fixed SIG_SEGV in check_stack() in eval.c Hi, In message "[PATCH] fixed SIG_SEGV in check_stack() in eval.c" on 04/05/22, b g writes: |I was getting a crash at 'JUMP_TAG(state);' in |check_stack() in eval.c because prot_tag was NULL. |The JUMP_TAG macro goes right after prot_tag without |checking it to be a valid pointer. *CRASH* | |Attached is my very simple fix. There's probly a |better way (I don't know why prot_tag is NULL in this |case, should it be?), but the patch below works for |me. It's probably caused by prot_tag left uninitialized by the application. Can you show us the portion of your application code that inistalize/call Ruby interpreter? matz.