unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 24764@debbugs.gnu.org
Subject: bug#24764: 25.1.50; Another crash in automatic gc
Date: Sat, 22 Oct 2016 17:24:44 +0300	[thread overview]
Message-ID: <8337joqx5f.fsf@gnu.org> (raw)
In-Reply-To: <87eg384gni.fsf@web.de> (message from Michael Heerdegen on Sat, 22 Oct 2016 16:12:01 +0200)

> From: Michael Heerdegen <michael_heerdegen@web.de>
> Cc: bug-gnu-emacs@gnu.org
> Date: Sat, 22 Oct 2016 16:12:01 +0200
> 
> Michael Heerdegen <michael_heerdegen@web.de> writes:
> 
> > That's one commit above emacs-25's current HEAD: the WIP commit for
> > making sort-line accepting a predicate arg.  I can revert it just to
> > be sure.  But I'm not even convinced that the stuff I suspect is
> > really the culprit.
> 
> FWIW, I already tried to compile (make bootstrap) with different
> versions of gcc (I downgraded all that stuff in Debian from testing to
> stable), and I checked out the emacs-25 branch from different points -
> but the crashs happened with every build.

Good to know.

Let's start with figuring out whether each crash shows the buffer's
marker chain overwritten by the same (or similar) text string.

In the session you have now, try this command, in frame #0:

 (gdb) p (char *)&b->markers

What does this print?  If it doesn't print any human-readable text,
try this:

 (gdb) p (char *)tail



  





  reply	other threads:[~2016-10-22 14:24 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-22  9:38 bug#24764: 25.1.50; Another crash in automatic gc Michael Heerdegen
2016-10-22 10:05 ` Eli Zaretskii
2016-10-22 11:41   ` Andreas Schwab
2016-10-22 12:01     ` Eli Zaretskii
2016-10-22 12:21       ` Eli Zaretskii
2016-10-22 14:05         ` Michael Heerdegen
2016-10-22 14:10           ` Eli Zaretskii
2016-10-22 14:43             ` Michael Heerdegen
2016-10-22 15:08               ` Eli Zaretskii
2016-10-22 18:25                 ` Michael Heerdegen
2016-10-22 18:35                   ` Eli Zaretskii
2016-10-23  9:06                     ` Michael Heerdegen
2016-10-23  9:32                       ` Eli Zaretskii
2016-10-23 10:22                         ` Eli Zaretskii
2016-10-23 10:53                           ` Michael Heerdegen
2016-10-23 12:06                             ` Eli Zaretskii
2016-10-23 10:49                         ` Michael Heerdegen
2016-10-23 10:24                       ` Eli Zaretskii
2016-10-23 11:00                         ` Michael Heerdegen
2016-10-23 12:08                           ` Eli Zaretskii
2016-10-23 13:57                           ` Eli Zaretskii
2016-10-23 15:53                             ` Michael Heerdegen
2016-10-23 16:37                               ` Michael Heerdegen
2016-10-23 17:01                                 ` Eli Zaretskii
2016-10-25 14:37                                   ` Michael Heerdegen
2016-10-25 16:46                                     ` Eli Zaretskii
2016-10-25 17:21                                       ` Michael Heerdegen
2016-10-25 18:17                                         ` Eli Zaretskii
2016-10-27 16:40                                         ` Michael Heerdegen
2016-10-27 17:18                                           ` Eli Zaretskii
2016-11-07  3:38                                           ` Eli Zaretskii
2016-11-07 11:36                                             ` Michael Heerdegen
2016-10-22 12:36       ` Eli Zaretskii
2016-10-22 13:54   ` Michael Heerdegen
2016-10-22 14:12     ` Michael Heerdegen
2016-10-22 14:24       ` Eli Zaretskii [this message]
2016-10-22 14:13     ` Eli Zaretskii
2016-10-23  9:32       ` Michael Heerdegen
2016-10-22 14:37 ` npostavs
2016-10-22 14:38   ` Eli Zaretskii
2016-10-22 14:51     ` Michael Heerdegen
2016-10-22 15:25       ` Eli Zaretskii
2016-10-22 15:33         ` 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

  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=8337joqx5f.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24764@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).