From: Quanah Gibson-Mount <quanah@stanford.edu>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Emacs 22.0.50 and suspending while logged into another system
Date: Mon, 16 Oct 2006 15:30:52 -0700 [thread overview]
Message-ID: <3243FAAFCFB33E8C91939813@deus-ex.stanford.edu> (raw)
In-Reply-To: <E1GYxUK-0007A1-TS@fencepost.gnu.org>
--On Sunday, October 15, 2006 12:20 AM -0400 Richard Stallman <rms@gnu.org>
wrote:
> In any case, you now have the information on what "tty" contained
> after it exited from EMACS_SET_TTY, and I'll leave it up to you and
> the other developers to decide whether or not that data was 'bad' or
> not.
>
> Did you examine that value just before the failure?
> That is, did it fail just after this call to init_sys_modes?
> init_sys_modes will be called each time you resume Emacs after
> suspending; the time that we need to see the value
> is the time that it fails.
>
> It would be good to see the value of tty after EMACS_SET_TTY,
> and the value of old_tty too.
Hi Richard,
I set up the following in gdb:
l sysdep.c:1637
break 1637
(this is the line after EMACS_SET_TTY is called in the source I have).
Then, I
run -nw
Then use control-Z to suspend.
This *usually* then breaks at line 1637. If this is where the break
occurs, everything continues to work as desired.
However, sometimes it breaks in _libc_kill instead, completely bypassing
EMACS_SET_TTY.
After this, things don't work correctly. So it appears that the same logic
is not always being followed when a SIGTSTP is caught.
The usual path I get is:
(control-Z):
Breakpoint 1, init_sys_modes () at sysdep.c:1642
1642 if (!flow_control) ioctl (input_fd, TCXONC, 1);
(gdb) cont
Program received signal SIGTSTP, Stopped (user).
0xfe6990cc in _poll () from /usr/lib/libc.so.1
(gdb)
Then I issue "signal SIGCONT" to resume.
On the other path:
(control-Z):
Program received signal SIGTSTP, Stopped (user).
0xfe69b638 in _libc_kill () from /usr/lib/libc.so.1
I tried "step"ing from here, but it just hangs forever, without entering
init_sys_modes.
I can reproduce this very easily. If I give a "signal SIGCONT" here, then
it'll let me back into emacs.
--Quanah
--
Quanah Gibson-Mount
Principal Software Developer
ITS/Shared Application Services
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html
next prev parent reply other threads:[~2006-10-16 22:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 22:45 Emacs 22.0.50 and suspending while logged into another system Quanah Gibson-Mount
2006-10-10 22:51 ` Kim F. Storm
2006-10-10 23:01 ` Quanah Gibson-Mount
2006-10-11 11:52 ` Kim F. Storm
2006-10-11 18:50 ` Richard Stallman
2006-10-11 19:49 ` Quanah Gibson-Mount
2006-10-12 15:02 ` Richard Stallman
2006-10-13 0:05 ` Quanah Gibson-Mount
2006-10-13 11:19 ` Richard Stallman
2006-10-13 18:52 ` Quanah Gibson-Mount
2006-10-15 4:20 ` Richard Stallman
2006-10-16 22:30 ` Quanah Gibson-Mount [this message]
2006-10-16 22:33 ` Quanah Gibson-Mount
2006-10-17 9:45 ` Richard Stallman
2006-10-17 11:00 ` Quanah Gibson-Mount
2006-10-17 18:40 ` Richard Stallman
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=3243FAAFCFB33E8C91939813@deus-ex.stanford.edu \
--to=quanah@stanford.edu \
--cc=bug-gnu-emacs@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 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.