From: "T.V Raman" <raman@google.com>
To: larsi@gnus.org
Cc: raman@google.com, emacs-devel@gnu.org
Subject: Re: Emacs: Segfault
Date: Thu, 2 Jun 2022 07:32:08 -0700 [thread overview]
Message-ID: <25240.51688.718427.86928@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <87k09zw3p4.fsf@gnus.org>
head as of last night.
Will try building again later.
Incidentally with the same crashing build:
I have been using make-thread in my emacs and emacspeak startup to
speed up emacs start time; taking those out avoids the crash.
It makes emacs startup slightly slower to do that -- though not
significantly so 0.34s vs 0.65s -- but if it helps catch errors ...
Lars Ingebrigtsen writes:
> "T.V Raman" <raman@google.com> writes:
>
> > This started happening yesterday on a build of emacs that has been
> > running happily on what is a new laptop --- build from May 30.
> >
> > I updated from HEAD and rebuilt emacs; but still get the segfault.
>
> [...]
>
> > #3 0x000055555578121d in read0 (readcharfun=<optimized out>,
> > locate_syms=<optimized out>) at lread.c:3683
>
> Is this with the current HEAD now? There were some reader-related
> things that were fixed some hours ago.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
> bloggy blog: http://lars.ingebrigtsen.no
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
--
Thanks,
--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1 🦮
next prev parent reply other threads:[~2022-06-02 14:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 14:01 Emacs: Segfault T.V Raman
2022-06-02 14:16 ` Lars Ingebrigtsen
2022-06-02 14:32 ` T.V Raman [this message]
[not found] ` <25240.51953.899261.444275@retriever.mtv.corp.google.com>
2022-06-02 14:40 ` Lars Ingebrigtsen
2022-06-02 15:47 ` T.V Raman
2022-06-02 16:16 ` T.V Raman
2022-06-02 16:42 ` Eli Zaretskii
2022-06-02 16:57 ` T.V Raman
2022-06-02 15:14 ` Mattias Engdegård
2022-06-02 15:24 ` T.V Raman
2022-06-02 16:30 ` Eli Zaretskii
2022-06-02 16:32 ` T.V Raman
2022-06-02 16:43 ` Eli Zaretskii
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=25240.51688.718427.86928@retriever.mtv.corp.google.com \
--to=raman@google.com \
--cc=emacs-devel@gnu.org \
--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.