From: "Andrés Ramírez" <rrandresf@gmail.com>
To: emacs-devel@gnu.org
Subject: help needed for getting a backtrace ( multi-head emacs_abort on lucid-frame)
Date: Sun, 17 Apr 2022 21:05:44 +0000 [thread overview]
Message-ID: <86mtgjh13r.fsf@gmail.com> (raw)
Hi.
The first time I used the --daemon command line option I got:
,---- [ ]
| Warning: due to a long standing Gtk+ bug
| https://gitlab.gnome.org/GNOME/gtk/issues/221
| Emacs might crash when run in daemon mode and the X11 connection is unexpectedly lost.
| Using an Emacs configured with --with-x-toolkit=lucid does not have this problem.
| Starting Emacs daemon.
`----
The output of that message lead me to the lucid toolkit.
Also the first time I did M-x report-emacs-bug I got:
,---- [ ]
| Please describe exactly what actions triggered the bug
| and the precise symptoms of the bug. If you can, give
| a recipe starting from `emacs -Q':
`----
That's the reason for trying to get a proper backtrace for this case.
Having said that this is the recipe for the missing backtrace:
source code: emacs-28.1.tar.xz
compiled emacs with: "--enable-checking=yes,glyphs --enable-check-lisp-object-type 'CFLAGS=-O0 -g3' --with-cairo --with-harfbuzz --with-modules --with-wide-int --with-x-toolkit=lucid --with-json=yes --with-xft"
--8<---------------cut here---------------start------------->8---
1. @host ./emacs -Q -f toggle-debug-on-error --daemon
2. @host emacsclient -c -n --eval '(eshell)'
3. on eshell-buffer emacs-version Return
4. @remoteMachine emacsclient -c -n ~/.bashrc {inside xterm} {JIC: be4 do 'ssh -Y user@host'} {.bashrc could have just a comment character}
5. M-x dired-jump
6. M-x eval-expression "(x-synchronize t)" {without the quotes}{when doing this step do not do #8}
7. M-x close-display-connection {both opened frames close, and emacs aborts. check trying to open a new-frame}
8. type exit and press Return on xterm. {this step depends on step#6}
--8<---------------cut here---------------end--------------->8---
Expected Output:
emacs crash {it's an emacs_abort}
Both opened frames close. #2 and #4
NOTE: when starting emacs without calling 'toggle-debug-on-error' after step#7 when You open a new
frame. You could get the message:
'X protocol error: RenderBadGlyph (invalid Glyph parameter) on protocol request 139'
For Trying to get backtrace I have appended those lines to the file
/tmp/emacs/src/emacs-28.1/src/.gdbinit
,---- [ ]
| #@theEndOf close-display-connection x-close-connection is called
| # b xfns.c:x-close-connection # does not work
| b xterm.c:x_delete_terminal
| b xterm.c:x_delete_display
| b terminal.c:delete_terminal
| b frame.c:delete_frame #very long function
| b sysdep.c:emacs_abort
| b emacs.c:terminate_due_to_signal
`----
Those breakpoints never get hitted.
Please. Let me know the right way of getting a backtrace on this
situation.
Best Regards
next reply other threads:[~2022-04-17 21:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-17 21:05 Andrés Ramírez [this message]
2022-04-17 23:59 ` help needed for getting a backtrace ( multi-head emacs_abort on lucid-frame) Po Lu
[not found] ` <87y203np3y.fsf@manco.pe>
[not found] ` <87v8v7kv9h.fsf@yahoo.com>
2022-04-18 3:52 ` andrés ramírez
2022-04-18 5:06 ` Po Lu
2022-04-18 5:40 ` andrés ramírez
2022-04-18 5:55 ` Po Lu
2022-04-18 6:16 ` andres.ramirez
2022-04-18 6:53 ` Po Lu
2022-04-18 7:37 ` andrés ramírez
2022-04-18 8:00 ` Po Lu
2022-04-18 8:14 ` andrés ramírez
2022-04-18 8:34 ` Po Lu
2022-04-18 8:49 ` andrés ramírez
2022-04-18 9:05 ` Po Lu
2022-04-18 9:32 ` andrés ramírez
2022-04-18 10:29 ` Po Lu
2022-04-18 13:57 ` andrés ramírez
2022-04-19 0:53 ` Po Lu
2022-04-19 20:44 ` andrés ramírez
2022-04-18 14:43 ` multi-head x error RenderBadGlyph on lucid-frame (was: help needed with backtrace ) andrés ramírez
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=86mtgjh13r.fsf@gmail.com \
--to=rrandresf@gmail.com \
--cc=emacs-devel@gnu.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).