all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andy Moreton <amoreton@solarflare.com>
Cc: 12402@debbugs.gnu.org
Subject: bug#12402: 24.2.50; Crash switching to ibuffer
Date: Mon, 10 Sep 2012 21:13:27 +0300	[thread overview]
Message-ID: <838vchlpa0.fsf@gnu.org> (raw)
In-Reply-To: <504E1EE2.7030605@solarflare.com>

> Date: Mon, 10 Sep 2012 18:09:54 +0100
> From: Andy Moreton <amoreton@solarflare.com>
> 
> On 10/09/2012 17:42, Eli Zaretskii wrote:
> >> Date: Mon, 10 Sep 2012 15:41:26 +0100
> >> From: Andy Moreton <amoreton@solarflare.com>
> >>
> >> During normal editing I tried to switch to the ibuffer buffer, and emacs
> >> aborted (backtrace below). Built from a clean bootstrap of r109965.
> >
> > Any chance of a repeatable recipe?
> >
> Alas no - I've not managed to get it to crash again. What would be useful to 
> look at if I can trigger another abort ?

The entire linked list of heaps, for starters, and the break_value.
The loop before the crash locus shows how:

  for (h = last_heap; h && break_value < h->end; h = h->prev)
    {
      excess += (char *) h->end - (char *) ((break_value < h->bloc_start)
					    ? h->bloc_start : break_value);
    }

I always thought that we should have only one heap on MS-Windows, so
first_heap and last_heap should be the same.  That's because on
Windows we reserve the entire range of addresses at startup, as a
single contiguous chunk.  But maybe I was mistaken...





  parent reply	other threads:[~2012-09-10 18:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-10 14:41 bug#12402: 24.2.50; Crash switching to ibuffer Andy Moreton
2012-09-10 16:42 ` Eli Zaretskii
     [not found]   ` <504E1EE2.7030605@solarflare.com>
2012-09-10 18:13     ` Eli Zaretskii [this message]
2012-09-19 21:49       ` Andy Moreton
2012-09-20  2:56         ` Eli Zaretskii
2012-09-20  3:24         ` Stefan Monnier
2012-10-07 18:35 ` Eli Zaretskii
2012-10-08 12:03   ` Andy Moreton
2012-10-08 12:34     ` 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=838vchlpa0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=12402@debbugs.gnu.org \
    --cc=amoreton@solarflare.com \
    /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.