all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: birdsite@airmail.cc
Cc: 50058@debbugs.gnu.org, larsi@gnus.org, birdsite@airmail.cc
Subject: bug#50058: 28.0.5; emacs build fails with undefined reference to malloc_info
Date: Sun, 15 Aug 2021 17:20:17 +0300	[thread overview]
Message-ID: <83fsvaaixq.fsf@gnu.org> (raw)
In-Reply-To: <85czqelvyl.fsf@laptop.i-did-not-set--mail-host-address--so-tickle-me> (birdsite@airmail.cc)

> From: birdsite@airmail.cc
> Cc: Flappy Bird <birdsite@airmail.cc>,  50058@debbugs.gnu.org,  Eli
>  Zaretskii <eliz@gnu.org>
> Date: Sun, 15 Aug 2021 18:28:30 +0545
> 
> git pull origin
> git checkout testing
> git reset --hard HEAD
> git pull         # pulls from local master
> make 2&> ../make-emacs-aug-15-head
> 
> This one fails with some segmentation fault.
> 
> 
> Loading subr (compiled; note, source file is newer)...
> Loading subr (compiled; note, source file is newer)...
> Fatal error 11: Segmentation fault
> Segmentation fault

Run the failing command under GDB and show the backtrace from the
segfault.

(To see which command fails, say "make V=1".)





      parent reply	other threads:[~2021-08-15 14:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14 13:41 bug#50058: 28.0.5; emacs build fails with undefined reference to malloc_info birdsite
2021-08-14 16:40 ` Eli Zaretskii
2021-08-14 17:08   ` Bird
2021-08-14 17:12   ` Lars Ingebrigtsen
2021-08-14 17:31     ` Eli Zaretskii
2021-08-14 17:39       ` Lars Ingebrigtsen
2021-08-15  1:59         ` Flappy Bird
2021-08-15 11:27           ` Lars Ingebrigtsen
2021-08-15 12:43             ` birdsite
2021-08-15 12:49               ` Lars Ingebrigtsen
2021-08-15 14:08                 ` birdsite
2021-08-15 14:20                   ` Lars Ingebrigtsen
2021-08-15 14:20               ` Eli Zaretskii [this message]

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=83fsvaaixq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=50058@debbugs.gnu.org \
    --cc=birdsite@airmail.cc \
    --cc=larsi@gnus.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 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.