all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ashish.is@lostca.se (Ashish SHUKLA)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 13864@debbugs.gnu.org
Subject: bug#13864: 24.3.50; emacsclient -t loops when connected to emacs server running in X11
Date: Mon, 25 Mar 2013 14:58:08 +0530	[thread overview]
Message-ID: <86li9bde1j.fsf@chateau.d.if> (raw)
In-Reply-To: <86y5e4xpd8.fsf@chateau.d.if>


[-- Attachment #1.1: Type: text/plain, Size: 2264 bytes --]

On Sun, 24 Mar 2013 21:54:04 +0200, Eli Zaretskii <eliz@gnu.org> said:

[...]


>  (gdb) break dispnew.c:2623 if vpos == 5

s/vpos/row/ I guess, which is what attached gdb output is with.

> This breakpoint is inside the make_current function:

>   static void
>   make_current (struct glyph_matrix *desired_matrix, struct glyph_matrix *current_matrix, int row)
>   {
>     struct glyph_row *current_row = MATRIX_ROW (current_matrix, row);
>     struct glyph_row *desired_row = MATRIX_ROW (desired_matrix, row);
>     bool mouse_face_p = current_row->mouse_face_p;

>     /* Do current_row = desired_row.  This exchanges glyph pointers
>        between both rows, and does a structure assignment otherwise.  */
>     assign_row (current_row, desired_row);

>     /* Enable current_row to mark it as valid.  */
current_row-> enabled_p = 1;
current_row-> mouse_face_p = mouse_face_p;  <<<<<<<<<<<<<<<<<<<<<<

> The choice of the line (5) is arbitrary.  Then wait until the
> breakpoint breaks, and do this:

>  (gdb) p current_row
>  $1 = (struct glyph_row *) 0x37e1158

> (The address will be different in your case.)  Now use that address to
> put a hardware watchpoint on the enabled_p flag of that glyph row, and
> continue the program:

>  (gdb) watch ((struct glyph_row *) 0x37e1158)->enabled_p
>  (gdb) c

> Now do whatever it takes to cause the flicker, and wait for the
> watchpoint to trigger, it should say something like

>  Hardware watchpoint 5: ((struct glyph_row *) 0x37e1158)->enabled_p

>  Old value = 1
>  New value = 0

> and will next show the source line which modified the value.  Then
> type

>  (gdb) bt

> and let it continue

>  (gdb) c

> Do this several times, each time waiting until the watchpoint
> triggers, and displaying the backtrace.  That should point towards the
> code which resets these flags and causes excessive re-drawing.

Please refer to the attached gdb output with annotations prefixed with '=====> '.

Thanks
-- 
Ashish SHUKLA

“It's good to be wrong. Don't feel shamed. Wear past mistakes as a badge of
honor because growth is everything. To stop learning is to decay.”
("apokalyptik", "in a conversation to abbe", 2010)

Sent from my Emacs

[-- Attachment #1.2: gdb.txt.xz --]
[-- Type: application/octet-stream, Size: 5140 bytes --]

[-- Attachment #2: Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2013-03-25  9:28 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-03 19:19 bug#13864: 24.3.50; emacsclient -t loops when connected to emacs server running in X11 Ashish SHUKLA
2013-03-04 17:50 ` Eli Zaretskii
2013-03-04 19:13   ` Ashish SHUKLA
2013-03-04 20:22     ` Eli Zaretskii
2013-03-05  0:26       ` Ashish SHUKLA
2013-03-06 17:07         ` Eli Zaretskii
2013-03-06 18:52           ` Ashish SHUKLA
2013-03-06 21:00             ` Eli Zaretskii
2013-03-07  1:43               ` Ashish SHUKLA
2013-03-07  6:55                 ` Eli Zaretskii
2013-03-07  7:38                   ` Ashish SHUKLA
2013-03-07  9:16                     ` Eli Zaretskii
2013-03-07 10:19                       ` Ashish SHUKLA
2013-03-07 12:48                         ` Eli Zaretskii
2013-03-08 10:08                           ` Ashish SHUKLA
2013-03-08 15:58                             ` Eli Zaretskii
2013-03-13  9:00                               ` Ashish SHUKLA
2013-03-15  9:39                                 ` Eli Zaretskii
2013-03-22 12:44                                   ` Ashish SHUKLA
2013-03-24 19:54                                     ` Eli Zaretskii
2013-03-25  9:28                                       ` Ashish SHUKLA [this message]
2013-03-25 10:56                                         ` Eli Zaretskii
2013-04-01 16:45                                           ` Ashish SHUKLA
2013-04-02 17:10                                             ` Eli Zaretskii
2013-04-10  9:06                                               ` Ashish SHUKLA
2013-04-10 15:41                                                 ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86li9bde1j.fsf@chateau.d.if \
    --to=ashish.is@lostca.se \
    --cc=13864@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.