unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Angelo Graziosi <angelo.g0@libero.it>
To: Paul Eggert <eggert@cs.ucla.edu>,
	Philippe Spiesser <ann.onymous@orange.fr>
Cc: Stefan Kangas <stefankangas@gmail.com>, 43152@debbugs.gnu.org
Subject: bug#43152: 28.0.50; when building emacs 28.0.50 ./temacs is stopped with core
Date: Thu, 3 Sep 2020 17:35:42 +0200 (CEST)	[thread overview]
Message-ID: <925561368.934706.1599147342379@mail1.libero.it> (raw)
In-Reply-To: <260fe7b3-3403-1fe2-8d89-31132af3e618@cs.ucla.edu>

> Il 02/09/2020 22:09 Paul Eggert ha scritto:
> 
>  
> Can you do a git bisect to see which commit is likely to have caused the problem?

I used the snapshots fro git repo and found that the first commit that fail is

Paul Eggert: Fix GC bug with Lisp floats and --with-wide-int

2ff930d861b772466b9f6b95d1776696298f3e0b 20200831_000556


The previous commit:

Stefan Kangas: Update Elisp Manual reference to which-function-mode

7605060d51bbce88307c09bd2e9be60f2750ee3d 20200831_043909

builds fine.

Ciao,
 Angelo.

(PS. Please, don't ask to use GDB...)





  parent reply	other threads:[~2020-09-03 15:35 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1457551226.863660.1599040446670@mail1.libero.it>
     [not found] ` <CADwFkmnymz3jBD41GjfONHAreqQgYDN2-5+sPfzEg5V0Yh=M=w@mail.gmail.com>
2020-09-02 20:09   ` bug#43152: 28.0.50; when building emacs 28.0.50 ./temacs is stopped with core Paul Eggert
2020-09-03 12:30     ` Anonymous
2020-09-03 15:35     ` Angelo Graziosi [this message]
2020-09-03 19:17       ` Paul Eggert
2020-09-03 23:17         ` Angelo Graziosi
2020-09-03 23:53           ` Angelo Graziosi
2020-09-04 20:32           ` Paul Eggert
2020-09-04 21:24             ` Angelo Graziosi
2020-09-04 21:34               ` Angelo Graziosi
2020-09-04 21:56               ` Paul Eggert
2020-09-05  6:30                 ` Angelo Graziosi
2020-09-05 12:05             ` Lars Ingebrigtsen
2020-09-05 19:27               ` Paul Eggert
2020-09-05 21:30                 ` Lars Ingebrigtsen
2020-09-06  0:58                   ` Paul Eggert
2020-09-06 11:50                     ` Lars Ingebrigtsen
2020-09-05 21:36                 ` Lars Ingebrigtsen
2020-09-05 21:41                 ` Lars Ingebrigtsen
2020-09-01  9:37 Philippe Spiesser
2020-09-01 11:10 ` Stefan Kangas
2020-09-01 14:19   ` Anonymous
2020-09-01 14:29   ` Eli Zaretskii
2020-09-01 16:49     ` Anonymous
2020-09-01 17:09       ` Eli Zaretskii
2020-09-01 17:15         ` Stefan Kangas
2020-09-02 10:00           ` Anonymous
2020-09-06 14:31 ` Mattias Engdegård
2020-09-06 14:38   ` Lars Ingebrigtsen
2020-09-06 15:44     ` Mattias Engdegård
2020-09-06 23:07       ` Lars Ingebrigtsen
2020-09-07  7:25         ` Mattias Engdegård
2020-09-07 10:20           ` Lars Ingebrigtsen
2020-09-07 12:24             ` Angelo Graziosi
2020-09-07 12:58     ` Anonymous

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=925561368.934706.1599147342379@mail1.libero.it \
    --to=angelo.g0@libero.it \
    --cc=43152@debbugs.gnu.org \
    --cc=ann.onymous@orange.fr \
    --cc=eggert@cs.ucla.edu \
    --cc=stefankangas@gmail.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 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).