unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Han Boetes <han@boetes.org>
Cc: 51689@debbugs.gnu.org
Subject: bug#51689: emacs
Date: Thu, 18 Nov 2021 09:13:04 +0200	[thread overview]
Message-ID: <83v90qx7gf.fsf@gnu.org> (raw)
In-Reply-To: <YZV2970X6nlMtyXM@boetes.org> (message from Han Boetes on Wed, 17 Nov 2021 22:41:11 +0100)

> Date: Wed, 17 Nov 2021 22:41:11 +0100
> From: Han Boetes <han@boetes.org>
> Cc: 51689@debbugs.gnu.org
> 
> > > >  features
> > > 
> > > I used c-h v features to get this output, is that what you meant? If not, please help me getting the requested information.
> > 
> > Is this in "emacs -Q -nw"?  There should be a feature defined by some
> > file from lisp/term/ loaded for the terminal support, but I see no
> > such feature.
> 
> I still don't understand how I should provide the requested features.
> Could you elaborate on that?

  . emacs -Q -nw
  . in *scratch* type "features" (without the quotes)
  . go to the end of "features", after the final 's', and type C-j
  . if the list Emacs inserts into the buffer has ellipsis in it, go
    to that ellipsis and type RET
  . post the resulting list here

> I just searched a bit further, it also happens with "emacs -nw
> some-file" when there is no .emacs file present, or if it contains only:
> 
>     (custom-set-variables)
> 
> But if that .emacs contains just one setting like this:
> 
>     (custom-set-variables '(auto-insert-mode t))
> 
> The problem is gone. Fascinating!

I think at this point only running under a debugger will help us
efficiently.  So please act according to the instructions below, and
show the backtrace it produces:

  $ cd /path/to/emacs/src/
  $ gdb ./emacs
  GNU gdb (GDB) 11.1
  Copyright (C) 2021 Free Software Foundation, Inc.
  ...
  (gdb) source ./.gdbinit
  (gdb) break Fsignal
  (gdb) commands
  Type commands for breakpoint(s) 2, one per line.
  End with a line saying just "end".
  > pp error_symbol
  > pp data
  > end
  (gdb) run -Q -nw

When the breakpoint breaks, look at the error_symbol and data printed
by GDB; if the symbol are not "void-function", type "continue" at
GDB's prompt to run Emacs further.  When you eventually get symbol as
"void-function" and data that mentions regexp-opt-group, type:

  (gdb) thread apply all bt

This should produce both C-level backtrace and Lisp-level backtrace of
all the threads in Emacs.  Please post that here in its entirety.

(I hope you have GDB installed; if not, please install it.)

Thanks.





  reply	other threads:[~2021-11-18  7:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-08 16:44 bug#51689: emacs Han Boetes
2021-11-08 18:15 ` Eli Zaretskii
2021-11-14 19:26 ` Eli Zaretskii
2021-11-14 21:20   ` Han Boetes
2021-11-15 12:33     ` Eli Zaretskii
2021-11-16  9:22       ` Han Boetes
2021-11-16 13:24         ` Eli Zaretskii
2021-11-17 17:45           ` Eli Zaretskii
2021-11-17 20:45             ` Han Boetes
2021-11-17 21:41           ` Han Boetes
2021-11-18  7:13             ` Eli Zaretskii [this message]
2021-11-19 22:18               ` Han Boetes
2021-11-20  9:36                 ` Eli Zaretskii
2021-11-20 14:59               ` Han Boetes
2021-11-20 15:15                 ` Eli Zaretskii
     [not found]                   ` <YZljMydhnoE0Di4p@boetes.org>
2021-11-21  6:31                     ` 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

  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=83v90qx7gf.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=51689@debbugs.gnu.org \
    --cc=han@boetes.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).