unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Uday S Reddy <u.s.reddy@cs.bham.ac.uk>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs 23.2.94 pretest
Date: Wed, 23 Feb 2011 14:01:40 -0500	[thread overview]
Message-ID: <87oc627ey3.fsf@stupidchicken.com> (raw)
In-Reply-To: <19813.18711.4000.254620@gargle.gargle.HOWL> (Uday S. Reddy's message of "Wed, 23 Feb 2011 17:51:19 +0000")

Uday S Reddy <u.s.reddy@cs.bham.ac.uk> writes:

> Chong Yidong writes:
>
>> Did you have any such problems with 23.2.93?
>
> No, I had an occasional crash, but nothing like this.

There are only about six changes between .93 and .94 that are likely to
create crashed where none previously existed.  If the crashes are
frequent enough, I suggest reverting each of these to see what makes a
difference.

Are you using the binaries, or building Emacs from source?  If the
latter, try individually reverting each of these in turn:

  100470
  100466
  100459
  100458
  100444
  100441

I can mail you the patches if you don't have access to bzr.  Running
Emacs in gdb and getting the backtrace, as Eli suggested, would also be
helpful.



  reply	other threads:[~2011-02-23 19:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-15  4:46 Emacs 23.2.94 pretest Chong Yidong
2011-02-15  4:54 ` Miles Bader
2011-02-15 15:49   ` Chong Yidong
2011-02-15 18:43     ` copyright-update in nnfolder [was Re: Emacs 23.2.94 pretest] Glenn Morris
2011-02-15 20:30       ` Stefan Monnier
2011-02-16  2:22       ` Miles Bader
2011-02-16 21:28     ` Emacs 23.2.94 pretest Lars Ingebrigtsen
2011-02-17  1:00 ` Sean Sieger
2011-02-23 17:36   ` Uday S Reddy
2011-02-23 17:44     ` Chong Yidong
2011-02-23 17:51       ` Uday S Reddy
2011-02-23 19:01         ` Chong Yidong [this message]
2011-02-23 19:27           ` Eli Zaretskii
2011-02-23 20:36           ` Uday S Reddy
2011-02-23 20:41             ` Lennart Borgman
2011-02-24  0:28               ` Christoph
2011-02-23 21:21             ` Chong Yidong
2011-02-23 21:51               ` Eli Zaretskii
2011-02-23 23:11                 ` Chong Yidong
2011-02-23 23:35                   ` Uday Reddy
2011-02-24  3:54                   ` Eli Zaretskii
2011-02-23 23:46               ` Uday S Reddy
2011-02-23 17:59     ` Eli Zaretskii
2011-02-24  1:13       ` Sean Sieger
2011-02-24  4:01         ` Eli Zaretskii
     [not found] ` <4D669A15.9080701@online.de>
2011-02-24 18:09   ` Chong Yidong
2011-02-24 18:56     ` Andreas Schwab
2011-02-24 21:26       ` Andreas Röhler
2011-02-24 22:20         ` Davis Herring
2011-02-25  6:46           ` Andreas Röhler
2011-02-25  9:32             ` Andreas Schwab
2011-02-25 10:09               ` Andreas Röhler
2011-02-25  7:01           ` Andreas Röhler
2011-02-25 13:35             ` Davis Herring
2011-02-25 10:18 ` Andreas Röhler
2011-02-25 10:29   ` Andreas Schwab
2011-02-25 11:31     ` Andreas Röhler
2011-02-25 11:43 ` Andreas Röhler

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=87oc627ey3.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=u.s.reddy@cs.bham.ac.uk \
    /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).