unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo via "Emacs development discussions." <emacs-devel@gnu.org>
To: "Gerry Agbobada" <gerry@gagbo.net>
Cc: "Emacs development discussions." <emacs-devel@gnu.org>
Subject: Re: [feature/native-comp] Segfaulting in push or nreverse ?
Date: Mon, 30 Nov 2020 20:03:51 +0000	[thread overview]
Message-ID: <xjfo8je4no8.fsf@sdf.org> (raw)
In-Reply-To: <457a0d97-fdaa-473e-9f7a-257d5792d70c@www.fastmail.com> (Gerry Agbobada's message of "Mon, 30 Nov 2020 17:47:10 +0100")

"Gerry Agbobada" <gerry@gagbo.net> writes:

> Hello,
>
> I've been using native-comp for a while and thanks for that. I think I found an issue with a seemingly simple function
> that only uses basic elisp procedures.
>
> * Issue
>
> When I run a specific rustic.el function while native-compiled, emacs segfaults; whereas if I delete the .eln file
> (rustic-flycheck.eln) and use the byte-compiled file instead, the function works as advertised.
>
> I've included the basic code to trigger the segfault and the source of the function for easier inspection
>
> * Reproduction
>
> 1) Install rustic.el
> 2) Native compile rustic.el
> 3) Run emacs -l rustic-segfault.el
>
> Regards,
>
> Gerry

Hi Gerry,

thanks for the bug report and for having already isolated the offending
function.  This looks fun :)

I've opened bug#44968 [1] so we can handle it there and we have record
of it.

  Andrea

[1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=44968



      reply	other threads:[~2020-11-30 20:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 16:47 [feature/native-comp] Segfaulting in push or nreverse ? Gerry Agbobada
2020-11-30 20:03 ` Andrea Corallo via Emacs development discussions. [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

  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=xjfo8je4no8.fsf@sdf.org \
    --to=emacs-devel@gnu.org \
    --cc=akrl@sdf.org \
    --cc=gerry@gagbo.net \
    /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).