gEDA-dev: Progress update on moving component selector (patch url)
Peter C.J. Clifton
pcjc2 at cam.ac.uk
Sat Sep 2 07:16:16 EDT 2006
On Sep 2 2006, Patrick Bernaud wrote:
>Hi again,
>
>Peter Clifton writes:
> > [...]
> > Just noticed that this happens in what I believe to be a clean CVS
> > build.
> >
> > Could someone please try repeating this for me:
> >
> > 1. Open the component selector (via the toolbar)
> > 2. Close the component selector (Close button)
> > 3. Goto 1. until crash (usually happens after a handful of times, less
> > than 10 I'd guess)
>
>It appears the new print_command field in TOPLEVEL was not initialized
>to NULL at TOPLEVEL creation. Fixed in CVS. It seems to work ok now,
>at least I can not make it crash anymore.
How did this affect the component selector?
Is it due to the preview window having its own TOPLELVEL, which is freed
when the component selector is opened and closed?
Regards
Peter C.
More information about the geda-dev
mailing list