unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: dhruva <dhruvakm@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs (HEAD) crash on M$ (XP) built with MinGW
Date: Mon, 20 Oct 2008 16:41:07 +0200	[thread overview]
Message-ID: <uprlvib24.fsf@gnu.org> (raw)
In-Reply-To: <e3f230850810200538va89266bx5b11c15d9323151a@mail.gmail.com>

> Date: Mon, 20 Oct 2008 18:08:15 +0530
> From: dhruva <dhruvakm@gmail.com>
> 
>  I am still seeing the elusive and infrequent crash. I open a 'C'
> file, maximize the frame and use the page down to scroll down or down
> arrow. I keep hitting this crash off and now. The tried getting 'xbt'
> and could not.

xbacktrace will not give you any useful information when the crash is
inside redisplay, at least not normally, because redisplay is not
normally triggered by Lisp code.  Redisplay is what Emacs normally
does when it is idle (on the C level).

> (gdb) bt
> #0  0x0103ca47 in next_element_from_string (it=0x82e1ac) at xdisp.c:6263
> #1  0x0103b03e in get_next_display_element (it=0x82e1ac) at xdisp.c:5655
> #2  0x0103591d in init_from_display_pos (it=0x82e1ac, w=0x38f0e00,
> pos=0x3af23e0) at xdisp.c:3035

Is this optimized build or unoptimized one?  If the former, please try
reproducing the crashes with unoptimized builds.  If this is already
unoptimized, please see what part(s) of the `it' structure caused the
crash, and show here their value(s).

If your xdisp.c is current, and assuming that this is an unoptimized
build (and so the backtrace is trustworthy), the problem seems to be
with trying to display something based on some string, which is stored
at it->string.  Could you please see what string is that, and what is
its contents?  That might give us a clue about whodunit.




  reply	other threads:[~2008-10-20 14:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 12:38 Emacs (HEAD) crash on M$ (XP) built with MinGW dhruva
2008-10-20 14:41 ` Eli Zaretskii [this message]
2008-10-21  3:42   ` dhruva
2008-10-21  5:40     ` dhruva
2008-10-21  5:58       ` dhruva
2008-10-21  6:38       ` Eli Zaretskii
2008-10-21  6:41       ` Eli Zaretskii
2008-10-21  7:11         ` dhruva
2008-10-21  7:41           ` Juanma Barranquero
2008-10-21  7:55             ` dhruva
2008-10-21  8:03               ` Juanma Barranquero
2008-10-21  8:30               ` Eli Zaretskii
2008-10-25 16:51                 ` dhruva
2008-10-25 16:56                   ` dhruva
2008-10-27  4:30                     ` dhruva
2008-10-27 20:09                       ` Eli Zaretskii
2008-10-28  4:00                         ` dhruva
2008-10-28  8:20                       ` Juanma Barranquero
2008-10-28 18:42                         ` Eli Zaretskii
2008-10-29  2:28                           ` Stephen J. Turnbull
2008-10-29  6:39                             ` Werner LEMBERG

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=uprlvib24.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dhruvakm@gmail.com \
    --cc=emacs-devel@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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).