GNU bug report logs - #9723
24.0.50; Emacs Clipboard crash

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Joseph Jones <josejones <at> expedia.com>
Cc: 9723 <at> debbugs.gnu.org
Subject: bug#9723: 24.0.50; Emacs Clipboard crash
Date: Sun, 12 Feb 2012 18:40:16 +0200

> From: Joseph Jones <josejones <at> expedia.com>
> CC: "9723 <at> debbugs.gnu.org" <9723 <at> debbugs.gnu.org>
> Date: Sat, 11 Feb 2012 17:50:41 -0800
> 
> *** Open Emacs in an NT cmd shell prompt. In Emacs, open up a cmd shell prompt. Start something that will cause a huge amount of text and scrolling. I run a build in the command prompt and then just wait for it to crash.

Any estimation of the length of output that is needed to have a crash?
Also, would just "type LARGE_SOME_FILE" do, for example?

> > #0  0x01259f9f in append_glyph (it=0x82ad3c) at term.c:1491
> 
> In this frame #0 of thread 1, what do the following commands produce?
> 
>   (gdb) print glyph
>   (gdb) print i
>   (gdb) print it->area
>   (gdb) print it->glyph_row->used[it->area]
> 
> ***
> (gdb) f 0
> #0  0x01259f9f in append_glyph (it=0x82acec) at term.c:1491
> 1491    in term.c
> (gdb) print glyph
> $1 = (struct glyph *) 0x0
> (gdb) print i
> $2 = 0
> (gdb) print it->area
> $3 = LEFT_MARGIN_AREA

This doesn't make any sense.  Maybe again some snafu with frame
dimensions?

Please type "source .gdbinit" (unless you started GDB from a directory
where that file lives), and then go to this frame:

  #4  0x012125ec in display_line (it=0x82c890) at xdisp.c:19369

and type these commands:

  (gdb) pit
  (gdb) print *it->w
  (gdb) pmtxrows it->w->current_matrix

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.