unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Andrea Corallo <akrl@sdf.org>
To: Jacob Faibussowitsch <jacob.fai@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, 62504@debbugs.gnu.org
Subject: bug#62504: 30.0.50; SEGFAULT On M-x
Date: Wed, 29 Mar 2023 15:27:35 +0000	[thread overview]
Message-ID: <xjflejffuhk.fsf@ma.sdf.org> (raw)
In-Reply-To: <B437A748-5BCE-4C1B-9593-2BDF1E792394@gmail.com> (Jacob Faibussowitsch's message of "Wed, 29 Mar 2023 08:29:06 -0400")

Jacob Faibussowitsch <jacob.fai@gmail.com> writes:

> Looks like I jumped the gun on blaming the segfaults on
> 52b67740d10df8ca539fdc2c7d50283997683141. They still happen before
> it. Interestingly they only appear to happen if the
> `(wrong-number-of-arguments #<subr signal> 2)` error has not fired.
>
> For example, my setup lazy-loads many packages (among them yasnippet
> and auto-complete) on an idle timer or eagerly if I invoke/reference
> an auto-loaded symbol. If I wait for the idle timer to lazy load
> e.g. yasnippet then I get `(wrong-number-of-arguments #<subr signal>
> 2)`. But if I try to eagerly load yasnippet via auto-load then I get a
> segfault instead.
>
> I don’t know how to reliably reproduce this unfortunately...
>
> Best regards,

Please try now after I reverted 4a7a0c9a9f5 263d6c38539.

  Andrea





  reply	other threads:[~2023-03-29 15:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 15:25 bug#62504: 30.0.50; SEGFAULT On M-x Jacob Faibussowitsch
2023-03-28 17:01 ` Eli Zaretskii
2023-03-29  8:49   ` Andrea Corallo
2023-03-29 12:29     ` Jacob Faibussowitsch
2023-03-29 15:27       ` Andrea Corallo [this message]
2023-03-29 15:31         ` Jacob Faibussowitsch
2023-09-11 23:56           ` Stefan Kangas

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=xjflejffuhk.fsf@ma.sdf.org \
    --to=akrl@sdf.org \
    --cc=62504@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jacob.fai@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).