One temporary hack is to turn off Container event handling by commenting
out the "addEvents(evtMap);" line. The problem appears to be in
callbacks that pass back a widget -- container signals just happen to do
this a lot. The assertion occurs because the widget handle is null when
we try to fetch it. I still haven't figured out why it's null, however.
Tom
On Wed, 2003-02-26 at 04:34, Mark Howard wrote:
> On Tue, 2003-02-25 at 22:02, Tom Ball wrote:
> > Is anyone else seeing the following repeated assertion failure?
>
> I get it all the time. Very often related to the text and tree widgets.
> I also get terrible performance when trying to enter text into text
> widgets, which I have so far assumed is related.
>
> > and it's getting called regularly. Any ideas why?
> Unfortunately not.
>
> possibly related:
> I tried debugging a crash which looked similar some time ago. It
> appeared as if the location of the peer was often randomly set to 0x14
> sometime during a glib call - the glib source code for this function
> could not have done this though.
> I always get crashes like this after any event occurs when running in
> either Blackdown 1.4.1beta or gcj natively compiled. (but kaffe works
> fine for me).
> Other people have also reported this crashing on the
>
> jav...@li...
> mailing list.
--
Tom Ball <Tom...@Su...>
|
