From: Andrea Corallo <akrl@sdf.org>
To: Sebastian Sturm <mail@sebastian-sturm.de>
Cc: 42088@debbugs.gnu.org
Subject: bug#42088: [feature/native-comp] Lockup on opening TypeScript files
Date: Sat, 27 Jun 2020 21:25:58 +0000 [thread overview]
Message-ID: <xjfzh8oryjd.fsf@sdf.org> (raw)
In-Reply-To: <b581d5dc-d9a6-0669-8631-f3b7fa886b0f@sebastian-sturm.de> (Sebastian Sturm's message of "Sat, 27 Jun 2020 18:55:28 +0200")
Sebastian Sturm <mail@sebastian-sturm.de> writes:
> Apologies in advance for this being a very vague bug report, but I
> don't know how to properly debug this kind of issue (pointers
> appreciated!)
Hi Sebastian,
no worries, at this stage we have finished the trivial bugs :)
I think the questions are two:
- Is Emacs just looping forever in
F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_10 or is does
something more complex?
- Where is F616e6f6e796d6f75732d6c616d626461_anonymous_lambda_10
defined? Being lambdas regular objects is can come from any
complilaiton unit.
I believe the easiest to answere is to compile using `comp-debug' 1 and
then while is hanging just trap with the gdb and see what is going on.
I managed to reproduce the issue, tomorrow I'll be curious to have a
look.
Thanks!
Andrea
--
akrl@sdf.org
next prev parent reply other threads:[~2020-06-27 21:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-27 16:55 bug#42088: [feature/native-comp] Lockup on opening TypeScript files Sebastian Sturm
2020-06-27 21:25 ` Andrea Corallo [this message]
2020-06-28 10:43 ` Andrea Corallo
2020-06-28 20:38 ` Andrea Corallo
2020-06-30 2:33 ` Stefan Monnier
2020-06-30 8:06 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-06-30 14:03 ` Stefan Monnier
2020-06-30 14:43 ` Andrea Corallo via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-06-29 21:01 ` Sebastian Sturm
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=xjfzh8oryjd.fsf@sdf.org \
--to=akrl@sdf.org \
--cc=42088@debbugs.gnu.org \
--cc=mail@sebastian-sturm.de \
/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.