Hello Peter, > > I'm not able to reproduce it either, nor is valgrind complaining when I > run a DRC. > > I'm hoping you will be able to find the missing backup file, and that we > can try reproducing the bug from that. >
Thanks for explanation about backups. my_filename.pcb- did not existed after the crash, I only had my original file. Crash happened shortly after starting pcb. > Any idea how the system was doing at the time it crashed? Could it have > been memory pressure which killed the process? > > How complex was the board? What kind of primitives did it contain? > Lines, pads, vias, polygons? I checked all logs and it's rather not possible that process was killed because of memory. Still there is "failed to create pixmap" output that I never noticed before. The board has about 150 elements, "any angle" tracks, 4 polygons and thermal tools. I remember that I run teardrops() shortly before, so there were arcs also. Now I hit something else (while still trying to reproduce original crash) and this time it can be reproduced: select element Shift-D (pinout window appears) click "close" on this window: Loading file 334a_tunning.pcb took 0.770000 The program 'pcb' received an X Window System error. This probably reflects a bug in the program. The error was 'BadDrawable (invalid Pixmap or Window parameter)'. (Details: serial 35022 error_code 9 request_code 134 minor_code 9) (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.) Is this pcb or my xorg installation? Stefan, Read my mail to the end. I'm not blaming developers, I'm asking about backups and reporting possible bug. Regards, Michael W. _______________________________________________ geda-user mailing list [email protected] http://www.seul.org/cgi-bin/mailman/listinfo/geda-user
