unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ami Fischman <ami@fischman.org>
Cc: 12745@debbugs.gnu.org
Subject: bug#12745: crash in bidi_pop_it during (idle) redisplay
Date: Mon, 29 Oct 2012 19:11:11 +0200	[thread overview]
Message-ID: <838vap8aq8.fsf@gnu.org> (raw)
In-Reply-To: <CAGKqTXW=KEcHJy47vVJYU7sYW4eVAWai+ExvQj2Ea=x=_4gJNA@mail.gmail.com>

> Date: Sun, 28 Oct 2012 21:26:55 -0700
> From: Ami Fischman <ami@fischman.org>
> Cc: 12745@debbugs.gnu.org
> 
> > If it loads the same .emacs, that is good enough.
> >
> 
> Ok, attached.

Thanks.

> (gdb) p current_buffer->name_
> $22 = 101548849
> (gdb) xtype
> Lisp_String
> (gdb) xstring current_buffer->name_
> $23 = (struct Lisp_String *) 0x60d8330
>   "cdm_wrapper.cc"

OK, so we were looking at the correct buffer.

> > Did that buffer have any minor mode or some other optional feature
> > turned on, in addition to C++ Mode?
> 
> 
> See attached b-g-e.txt, in which the current buffer is the same .cc file in
> my HEAD session loading the same .emacs as the crashed one.

Fwew!  There are quite a few minor modes you have turned on that use
overlays to do their job.  Coupled with the fact that the problem
happens after hours of work, I don't think a reproducible recipe will
be possible any time soon.  Hmmm...

> > So are you debugging a core dump?
> >
> 
> Yes.

Well, I hope that now you are running under GDB to begin with, because
debugging a live Emacs process is so much easier than debugging a core
dump.

Thanks.





  reply	other threads:[~2012-10-29 17:11 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-28  3:31 bug#12745: crash in bidi_pop_it during (idle) redisplay Paul Eggert
2012-10-28  7:49 ` Paul Eggert
2012-10-28  7:50 ` Paul Eggert
2012-10-28 17:23   ` Eli Zaretskii
2012-10-28 19:00     ` Ami Fischman
2012-10-28 19:50       ` Eli Zaretskii
2012-10-29  4:26         ` Ami Fischman
2012-10-29 17:11           ` Eli Zaretskii [this message]
2012-10-29 17:56             ` Ami Fischman
2012-10-29 18:10               ` Eli Zaretskii
2012-10-29 18:29                 ` Ami Fischman
2012-10-29 18:55                   ` Eli Zaretskii
2012-10-29 18:56                   ` Alp Aker
2012-10-29 19:09                     ` Alp Aker
2012-10-29 19:23                       ` Ami Fischman
2012-10-29 20:24                         ` Eli Zaretskii
2012-10-29 20:57                           ` Eli Zaretskii
2012-10-29 21:08                             ` Ami Fischman
2012-10-30 17:52                           ` Eli Zaretskii
2012-10-30 18:29                             ` Ami Fischman
2012-10-30 21:00                               ` Eli Zaretskii
2012-10-30 21:08                                 ` Ami Fischman
2012-10-31 15:46                                   ` Eli Zaretskii
2012-11-01 22:25                                     ` Ami Fischman
2012-11-02  7:17                                       ` Eli Zaretskii
2012-11-02  7:43                                         ` Ami Fischman
2012-11-03  9:31                                     ` Eli Zaretskii
2012-10-29 20:25                       ` Eli Zaretskii
2012-10-29 20:42                         ` Alp Aker
2012-10-29 20:59                           ` Eli Zaretskii
2012-10-29 21:25                             ` Alp Aker
2012-10-29 21:53                               ` Alp Aker
2012-11-23 20:14 ` Ami Fischman
2012-11-23 21:56   ` Eli Zaretskii
2012-11-25  4:52     ` Ami Fischman
2012-11-25 16:51       ` Eli Zaretskii
2013-02-10  3:07       ` Glenn Morris

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=838vap8aq8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12745@debbugs.gnu.org \
    --cc=ami@fischman.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).