> Could you try doing (x-synchronize t) and then making it crash?
> That way, the crash will happen WITHIN the X primitive that causes
> the error.
No problem.
--=-=-=
Content-Disposition: attachment; filename=backtrace_0105.txt
Content-Description: backtrace_0105.txt
#0 0x4d5967ca in XtWidgetToApplicationContext () from /usr/lib/libXt.so.6
#1 0x4d59eb5f in XtGetValues () from /usr/lib/libXt.so.6
#2 0x080d1630 in x_wm_set_size_hint (f=0xb245f48, flags=0, user_position=0)
at xterm.c:9749
Now you can look at the data in the X error packet
and see what caused the error. By comparing this with the arguments
to these calls, you can find out what is invalid in the arguments.
When you report that, someone should be able to fix the bug.
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
