Re: A crash in a gnus group with indic script in content and headers

[Manoj Srivastava]

On Thu, Oct 23 2008, Kenichi Handa wrote:

> In article <address@hidden>, Manoj Srivastava <address@hidden> writes:
>
>>         I think the font name is not in font, that seems to be an
>>  integer. I have left the gdb session running, in case you want me to
>>  try something else.
>
> Did you start gdb in the C source directory of Emacs?
>
> --- from etc/DEBUG ---
> ** When you debug Emacs with GDB, you should start it in the directory
> where the executable was made.  That directory has a .gdbinit file
> that defines various "user-defined" commands for debugging Emacs.
> (These commands are described below under "Examining Lisp object
> values" and "Debugging Emacs Redisplay problems".)
> ------------------------------------------------------------
>
> In .gdbinit, the command "pr" is defined to print Lispy value.

        Sorry. I'll retry running gdb from the src directory, instead of
 the top.

> By the way,
>
>> (gdb) print font
>> $5 = 38342148
>> (gdb) ptype font
>> type = long int
>
> Ummm, you are using 64-bit system, right?  I suspect the
> problem is here.  Perhaps some of font handling code of
> Emacs (or libotf) has a bug for 64-bit system.
>
> I currently can not use 64-bit machine.  Can you test Emacs
> on 32-bit machine?

        I no longer own a 32-bit machine with a display. I have a
 headless firewall and file server, and I'll see if I can setup gnus to
 run on those machines.

        manoj
-- 
My cup hath runneth'd over with love.
Manoj Srivastava <address@hidden> <http://www.golden-gryphon.com/>  
1024D/BF24424C print 4966 F272 D093 B493 410B  924B 21BA DABB BF24 424C