From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: 58104@debbugs.gnu.org
Subject: bug#58104: 29.0.50; Emacs crushers in console probably by M-w
Date: Tue, 27 Sep 2022 09:42:51 +0300 [thread overview]
Message-ID: <83mtaljp1w.fsf@gnu.org> (raw)
In-Reply-To: <868rm55pwi.fsf@protected.rcdrun.com> (message from Jean Louis on Tue, 27 Sep 2022 08:48:13 +0300)
> From: Jean Louis <bugs@gnu.support>
> Date: Tue, 27 Sep 2022 08:48:13 +0300
>
>
> I am running Emacs from console by using gdb, so it crashed when I used
> M-w but cannot remember how exactly. I select something, I can see
> selected text in blue, and I run gdb in console with gdb --args emacs -Q
> -nw then Emacs receives some signal, sometimes, I caught something:
>
> (gdb) backtrace
> #0 0x00007ffff60192b1 in pselect () at /usr/lib/libc.so.6
> #1 0x00005555557db811 in really_call_select (arg=0x7fffffffca10) at thread.c:612
> #2 0x00005555557dbf8f in flush_stack_call_func (arg=0x7fffffffca10, func=0x5555557db7a0 <really_call_select>)
> at /home/data1/protected/Programming/Software/emacs/src/lisp.h:4225
> #3 thread_select
> (func=<optimized out>, max_fds=max_fds@entry=9, rfds=rfds@entry=0x7fffffffcb10, wfds=wfds@entry=0x7fffffffcb90, efds=efds@entry=0x0, timeout=timeout@entry=0x7fffffffd170, sigmask=<optimized out>) at thread.c:644
> #4 0x00005555557ffe0d in xg_select
> (fds_lim=9, rfds=0x7fffffffd2a0, wfds=0x7fffffffd320, efds=0x0, timeout=<optimized out>, sigmask=0x0) at xgselect.c:184
> #5 0x00005555557b332b in wait_reading_process_output
> (time_limit=time_limit@entry=30, nsecs=nsecs@entry=0, read_kbd=read_kbd@entry=-1, do_display=do_display@entry=true, wait_for_cell=wait_for_cell@entry=0x0, wait_proc=wait_proc@entry=0x0, just_wait_proc=<optimized out>) at process.c:5685
> #6 0x00005555555afe90 in sit_for (timeout=timeout@entry=0x7a, reading=reading@entry=true, display_option=display_option@entry=1)
> at dispnew.c:6238
> #7 0x00005555556dd8b7 in read_char
> (commandflag=1, map=0x555555fb4c93, prev_event=0x0, used_mouse_menu=0x7fffffffda6b, end_time=0x0)
> at /home/data1/protected/Programming/Software/emacs/src/lisp.h:761
Is this a backtrace from the crash, or is this just a backtrace after
attaching GDB to a running Emacs? It doesn't look to me as a crash.
It looks like Emacs is idle waiting for input.
Is the crash reproducible?
next prev parent reply other threads:[~2022-09-27 6:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 5:48 bug#58104: 29.0.50; Emacs crushers in console probably by M-w Jean Louis
2022-09-27 6:42 ` Eli Zaretskii [this message]
2022-09-27 20:18 ` Jean Louis
2022-09-28 2:32 ` Eli Zaretskii
2022-09-28 9:09 ` Jean Louis
2022-09-28 11:57 ` Eli Zaretskii
2022-10-01 3:56 ` Jean Louis
2022-10-01 6:27 ` Eli Zaretskii
2022-10-05 18:50 ` Jean Louis
2022-10-05 19:24 ` Eli Zaretskii
2022-10-05 19:43 ` Jean Louis
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=83mtaljp1w.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58104@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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).