From: Eli Zaretskii <eliz@gnu.org>
To: dhruva <dhruvakm@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Problem with Emacs HEAD on WXP (-nw)
Date: Fri, 31 Aug 2007 00:04:55 +0300 [thread overview]
Message-ID: <uk5rcbuo8.fsf@gnu.org> (raw)
In-Reply-To: <e3f230850708300602o3a74af59lc6275db21dc13d06@mail.gmail.com> (message from dhruva on Thu, 30 Aug 2007 18:32:04 +0530)
> Date: Thu, 30 Aug 2007 18:32:04 +0530
> From: dhruva <dhruvakm@gmail.com>
>
> I updated with the latest sources from HEAD and built with MinGW on WXP.
> "emacs -q -nw" and it hangs. I ran it through gdb, I am not able to
> interrupt (CTRL-C) it to get a backtrace either.
Does it help to type Ctrl-BREAK instead of Ctrl-C?
Also, what about attaching GDB to an already running (and stuck)
Emacs? does that help?
prev parent reply other threads:[~2007-08-30 21:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 13:02 Problem with Emacs HEAD on WXP (-nw) dhruva
2007-08-30 15:24 ` Dan Nicolaescu
2007-08-30 21:04 ` Eli Zaretskii [this message]
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=uk5rcbuo8.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dhruvakm@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).