From: Luis Lavena Date: 2007-11-16T00:50:37+09:00 Subject: Re: [PATCH] mswin32-vc6 segmentation fault due ruby_in_eval wrong definition On Nov 15, 2007 12:44 PM, Nobuyoshi Nakada wrote: > Hi, > > At Thu, 15 Nov 2007 15:42:23 +0900, > Luis Lavena wrote in [ruby-core:13536]: > > Working in collaboration with Aman Gupta, we were trying to make > > ParseTree on Windows a fully working gem+extension. During the process > > of testing the changes, we found a segmentation fault raised by the C > > extension in ruby_in_eval increment: > > Why do you need to access it? To create AST without executing? > If so, wouldn't a new function to do it be better than a global > variable? > Nobu, thank you for answering. ruby_in_eval is present in the original ParseTree code, wasn't my choice (since there is a good reason why isn't properly exported). Anyway, it seems that without the fix, ruby_in_eval points to some garbage memory, which make the segmentation fault. I don't know how this managed to work under *nix... -- Luis Lavena Multimedia systems - Leaders are made, they are not born. They are made by hard effort, which is the price which all of us must pay to achieve any goal that is worthwhile. Vince Lombardi