Subject: bug#7949: 24.0.50; GNU Emacs with Xaw3d does not launch as X client

From: Peter Dyballa <[email-masked]>
Date: Thu, 3 Feb 2011 16:18:21 +0100

Am 03.02.2011 um 14:47 schrieb Jan Djärv:

> 2011-02-03 11:58, Peter Dyballa skrev:
>>
>> Am 01.02.2011 um 08:20 schrieb Jan Djärv:
>>
>>> This is supposing the error handler is invoked.
>>
>>
>> Is the error handler invoked? If so, it does not seem to work.  
>> Xterm or xfd
>> clearly say that the font cannot be loaded and quit. Why is GNU  
>> Emacs spinning
>> around in something like an infinite loop?
>>
>> Jeremy Huddleston keeps saying:
>>
>>> Now the reason emacs is spinning is because it's not handling the  
>>> error
>>> correctly. It's calling XSync() from within its x_error_handler().
>>
>
> It turns out that XtCloseDisplay also calls XSync.  I removed all  
> XSync from the error handler.  Can you try with a frech checkout  
> from trunk?

Jan,

to avoid possible misunderstandings: Since I removed (and then  
corrected to iso8859-1 encoding) one X resource, all my Xaw3d X  
clients of GNU Emacs launch. Only in gdb it halted with the once  
modified xterm.c *while* that resource was set.

So my task is to check whether GNU Emacs launches from gdb when that  
faulty resource is set? (which can be accomplished by running it with  
arguments "-xrm '*synchronous: true' -xrm '*pane.menubar.font: - 
linotype-optima-black-*-*-*-10-*-*-*-*-*-iso10646-1'")

--
Greetings

   Pete

Never be led astray onto the path of virtue