unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Paul Eggert <paul.eggert@verizon.net>
Cc: Glenn Morris <rgm@gnu.org>, 33709@debbugs.gnu.org
Subject: bug#33709: Hang when compiled with --coverage and gcc 7.3
Date: Mon, 31 Aug 2020 10:36:36 +0000	[thread overview]
Message-ID: <CADwFkm=svpW8wnuLdHMwnqKtZ5KKjn4Oox48k=dNV8t=2Ty0ow@mail.gmail.com> (raw)
In-Reply-To: <b6cdab6b-0794-7eeb-d37e-84d6a3e6afb4@verizon.net> (Paul Eggert's message of "Thu, 27 Dec 2018 20:06:56 -0800")

Paul Eggert <paul.eggert@verizon.net> writes:

> I'm surprised that --coverage ever worked in a dumped emacs. I think libgcov
> uses the dynamic linker's malloc (so Emacs has *three* malloc implementations)
> and our trick for switching from the Emacs malloc in temacs to the system malloc
> in bootstrap-emacs won't work for memory allocated for
> --coverage. Unfortunately, the libgcov actions do not seem to be easy to disable
> in temacs and re-enable in bootstrap-emacs.
>
> I suggest that we just say this combination isn't supported; if you want to
> build Emacs with gcc --coverage you can configure with CANNOT_DUMP=yes.
>
> If the portable dumper ever gets working, --coverage should be easy to support,
> of course.

(That was 1.5 years ago.)

Any updates here now that we have the portable dumper?  Thanks.





  reply	other threads:[~2020-08-31 10:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 18:59 bug#33709: Hang when compiled with --coverage and gcc 7.3 Glenn Morris
2018-12-11 19:27 ` Eli Zaretskii
2018-12-11 19:46   ` Glenn Morris
2018-12-11 20:37     ` Glenn Morris
2018-12-13 19:40       ` Glenn Morris
2018-12-13 19:54         ` Eli Zaretskii
2018-12-28  4:06 ` Paul Eggert
2020-08-31 10:36   ` Stefan Kangas [this message]
2022-01-29 15:18 ` Lars Ingebrigtsen
2022-01-29 19:18   ` Glenn Morris

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='CADwFkm=svpW8wnuLdHMwnqKtZ5KKjn4Oox48k=dNV8t=2Ty0ow@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=33709@debbugs.gnu.org \
    --cc=paul.eggert@verizon.net \
    --cc=rgm@gnu.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 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).