Re: gEDA-user: GTK PCB crashes with losing the data

[Karel Kulhavy <clock@xxxxxxxxxxxxx>]

On Sun, Mar 26, 2006 at 07:37:59AM -0500, Stuart Brorson wrote:
> Karel,
> 
> I can't help you with your bug.  However, I think you might help the
> developers a little bit by offering these pieces of info:
> 
> GTK version
> glib version

clock@kestrel:~$ pkg-config --version gtk
0.20
clock@kestrel:~$ pkg-config --version glib
0.20

CL<
> 
> I know from experience that some versions of GTK were buggy -- the
> callback system was messed up and the pointers to the calling function
> would get messed up on the stack as one function called the next
> ... called the next ... called the next....  If you are running an
> older version of GTK (2.0 or even 2.2), you might be experiencing a
> GTK problem.
> 
> Stuart
> 
> 
> > 
> > I was drawing a schematic. Suddely PCB crashed with the following errors
> > and destroyed my unsaved work. The windowmanager is fvwm. pcb-bin:
> > 20050609
> > 
> > I don't know whether the "** Message: GotoError: ChangeGroupVisibility
> > (GetLayerNumber" errors were produced during the crash or during
> > previous work.
> > 
> > clock@kestrel:~/creat/ronja/trunk/schematics$ pcb twister2.pcb
> > ** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
> > ** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
> > ** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
> > ** Message: GotoError: ChangeGroupVisibility (GetLayerNumber
> > The program 'pcb-bin' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadRequest (invalid request code or no such operation)'.
> >   (Details: serial 25054107 error_code 1 request_code 0 minor_code 0)
> >   (Note to programmers: normally, X errors are reported asynchronously;
> >    that is, you will receive the error a while after causing it.
> >    To debug your program, run it with the --sync command line
> >    option to change this behavior. You can then get a meaningful
> >    backtrace from your debugger if you break on the gdk_x_error()
> > function.)
> > The program 'pcb-bin' received an X Window System error.
> > This probably reflects a bug in the program.
> > The error was 'BadRequest (invalid request code or no such operation)'.
> >   (Details: serial 25054110 error_code 1 request_code 0 minor_code 0)
> >   (Note to programmers: normally, X errors are reported asynchronously;
> >    that is, you will receive the error a while after causing it.
> >    To debug your program, run it with the --sync command line
> >    option to change this behavior. You can then get a meaningful
> >    backtrace from your debugger if you break on the gdk_x_error()
> > function.)
> > 
> > CL<
> >