[Vm-dev] Re: SegmentationFault in with OmniBrowser
damien.cassou at gmail.com
Tue May 22 14:23:01 UTC 2007
2007/5/22, Lukas Renggli <renggli at gmail.com>:
> > > has a very good chance to trigger such problems. And indeed: Once you do
> > > this you get an error saying that instances of OBModalFilter aren't
> > > indexable which is raised during simulating OBModalFilter>>selection:.
> > > Looking at the bytecodes (or the decompile) of that method shows that
> > > there is indeed a major problem, plus in a couple of other methods
> > > (noteParent:child: for example).
> > Not that easy to me. I did not understand a word of what you explained.
> The compiled method accesses a non-existing instance-variable.
Much clearer :-) However, when methods access a non existing instance
variable, I think it should not crash the VM with a segfault.
> > > How it got into this state is a great question, though. Somewhere,
> > > somehow your system is badly screwed up. Given that you have some fairly
> > > experimental Monticello changes in there I think it's a fair guess to
> > > assume that those might be causing the problem.
> > You should not assume I have a special Monticello version, it's not
> > the case. I have the Monticello included in 3.10 (maybe this one is
> > experimental, I don't know).
> This probably has to do with the recent changes of Monticello that
> somehow changes the way how code is loaded and changes the
> change-notification mechanism. It works in 3.9.
I think Keith's changes have NOT been integrated into 3.10.
More information about the Vm-dev