all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuri D'Elia <wavexx@thregr.org>
Cc: 26153@debbugs.gnu.org
Subject: bug#26153: 26.0.50; Garbage displayed at visual line boundaries
Date: Sat, 18 Mar 2017 20:04:13 +0200	[thread overview]
Message-ID: <831stuxy02.fsf@gnu.org> (raw)
In-Reply-To: <87k27m5vg0.fsf@wavexx.thregr.org> (message from Yuri D'Elia on Sat, 18 Mar 2017 18:46:55 +0100)

> From: Yuri D'Elia <wavexx@thregr.org>
> Cc: 26153@debbugs.gnu.org
> Date: Sat, 18 Mar 2017 18:46:55 +0100
> 
> On Sat, Mar 18 2017, Yuri D'Elia wrote:
> > Uhm, old versions fail to build at the dumping step for me.
> > I guess because of the change in glibc's malloc?
> 
> On some versions gmalloc fails to build.
> On others, dumping just fails with a segmentation fault.
> 
> I cannot bisect easily like this.

Sorry about that.  Did you try configuring with REL_ALLOC=no?  That
is,

  REL_ALLOC=no ./configure ...

This should avoid at least the problems with segfaults during dumping.





  reply	other threads:[~2017-03-18 18:04 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18 12:00 bug#26153: 26.0.50; Garbage displayed at visual line boundaries Yuri D'Elia
2017-03-18 13:28 ` Eli Zaretskii
2017-03-18 14:28   ` Yuri D'Elia
2017-03-18 14:43     ` Eli Zaretskii
2017-03-18 16:22       ` Yuri D'Elia
2017-03-18 16:44         ` Eli Zaretskii
2017-03-18 17:10           ` Yuri D'Elia
2017-03-18 17:15             ` Eli Zaretskii
2017-03-18 17:23               ` Yuri D'Elia
2017-03-18 17:46         ` Yuri D'Elia
2017-03-18 18:04           ` Eli Zaretskii [this message]
2017-03-18 19:31             ` Yuri D'Elia
2017-03-18 19:34               ` Eli Zaretskii
2017-03-18 19:42                 ` Yuri D'Elia
2017-03-18 19:50                   ` Eli Zaretskii
2017-03-18 13:58 ` Eli Zaretskii
2017-03-18 14:25   ` Yuri D'Elia

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=831stuxy02.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=26153@debbugs.gnu.org \
    --cc=wavexx@thregr.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.