Subject: Re: bug#10035: Crash in check_x_frame in w32fns.c

From: Christoph Scholtes <[email-masked]>
Date: Sun, 13 Nov 2011 13:55:30 -0700

On 11/13/2011 1:21 PM, Eli Zaretskii wrote:

> Sorry, I meant to type this in frame #2, where a and be are arguments
> of the function row_equal_p:
>
>> #2  0x010ee0d5 in row_equal_p (a=0x10dc2158, b=0x10d97158, mouse_face_p=1)
>>       at dispnew.c:398

(gdb) p a->enabled_p
$2 = 1
(gdb) p b->enabled_p
$3 = 1

> Btw, what's up with the messed up line numbers in dispnew.c?  Observe:
>
>    #2  0x010ee0d5 in row_equal_p (a=0x10dc2158, b=0x10d97158, mouse_face_p=1)
>         at dispnew.c:398
>    #3  0x010f490f in scrolling_window (w=0x10d96000, header_line_p=0)
>         at dispnew.c:398
>    #4  0x010f30fe in update_window (w=0x10d96000, force_p=1) at dispnew.c:398
>    #5  0x010f27fe in update_window_tree (w=0x10d96000, force_p=1)
>         at dispnew.c:398
>    #6  0x010f27d7 in update_window_tree (w=0x10d72200, force_p=1)
>         at dispnew.c:398
>    #7  0x010f254d in update_frame (f=0x3a24e00, force_p=1, inhibit_hairy_id_p=0)
>         at dispnew.c:398
>
> We are obviously very smart if we succeeded to squeeze all these
> functions into a single source line ;-)

Interesting. I didn't notice that.

> What version of GCC is that?

tdm-gcc 4.6.1