|
From: Dale A. <da...@gr...> - 2009-10-02 02:26:56
|
I entered a patch to fix this, see tracker 2871624. I did some more investigation, and it turns out that context.parent can be null. The patch checks for this case, and if the parent is null, it just continues to use the same context. So far, this seems to be working fine. Dale On Wed, Sep 30, 2009 at 1:07 PM, Alan Ezust <ala...@gm...> wrote: > I've seen an NPE there from time to time also, but I can't reproduce it. > > On Wed, Sep 30, 2009 at 11:50 AM, Dale Anson <da...@gr...> wrote: >> >> On Wed, Sep 30, 2009 at 9:58 AM, Matthieu Casanova >> <cho...@gm...> wrote: >> > But in that code, the fields are used as parameters, so filling the >> > keyword >> > field at line 294 is used to highlight tokens, removing that will lead >> > to >> > bugs. >> > For the NPE at line 294, do you know if it is because of context being >> > null >> > or context.rules ? >> >> I don't know. I didn't look into it far enough. I supposed, though, >> if I'm the only one seeing this issue, that means I've got something >> wrong somewhere. >> > > |