all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Live System User <nyc4bos@aol.com>
To: emacs-devel@gnu.org
Cc: Eli Zaretskii <eliz@gnu.org>
Subject: Re: Does anybody know how to debug a live Emacs process?
Date: Thu, 28 Apr 2016 06:24:36 -0400	[thread overview]
Message-ID: <87inz2vxnf.fsf@aol.com> (raw)
In-Reply-To: 83d1paxijn.fsf@gnu.org

Eli Zaretskii <eliz@gnu.org> writes:
Hi,
>> From: Live System User <nyc4bos@aol.com>
>> Date: Thu, 28 Apr 2016 02:37:17 -0400
>> 
>> I have a live Emacs process that is stuck in a state which only
>> displays:
>> 
>>          Invalid argument #<terminal 2> in ‘get-device-terminal’
>> 
>> in the echo area, including when trying to execute M-x.
>> 
>> I was hoping to solicit assistance to help obtain information to
>> help Emacs and opened Bug#23378 on Monday.
>
> Attach the debugger to the running process, like this:
>
>   gdb -p PID
>
> where PID is the process number of the Emacs process, you should be
> able to see it in the display produced by the 'top' or 'ps' command.
>
> If GDB succeeds in attaching to the process, it will stop it and
> display a "(gdb)" prompt.  Then type at that prompt:
>
>   thread apply all bt full
>
> Then file a bug report with everything that was displayed by GDB.
>
> Some additional information about debugging Emacs is available in the
> file etc/DEBUG that is part of the distribution.

I've added the GDB backtrace info to Bug#23378, as requested.

Thanks.




  reply	other threads:[~2016-04-28 10:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-28  6:37 Does anybody know how to debug a live Emacs process? Live System User
2016-04-28  8:07 ` Eli Zaretskii
2016-04-28 10:24   ` Live System User [this message]
2016-04-29 18:18   ` Live System User
2016-04-29 18:35     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87inz2vxnf.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=eliz@gnu.org \
    --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 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.