unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Kyle M. Lee" <mail2kyle@gmail.com>
Cc: emacs-pretest-bug@gnu.org
Subject: Re: 23.0.60; emacs hangs on WinXP with --disable-font-backend, and backtrace
Date: Wed, 07 May 2008 21:15:25 +0300	[thread overview]
Message-ID: <uk5i6dlqa.fsf@gnu.org> (raw)
In-Reply-To: <4821EE06.9040409@gmail.com>

> Date: Thu, 08 May 2008 01:59:34 +0800
> From: "Kyle M. Lee" <mail2kyle@gmail.com>
> Cc: 
> 
> (gdb) r

Please try "r -Q", otherwise your ~/.emacs comes into play, and we
have no way of knowing what's in it.

> Starting program: E:\cvs_home\emacs23\emacs\src/.\emacs.exe
> [New thread 5048.0x1270]
> [New thread 5048.0x13bc]
> [New thread 5048.0x3e4]
> 
> Program exited normally.

How did it "exit normally"? did you type "C-x C-c" to exit Emacs, or
did it exit on its own?

> (gdb) r --disable-font-backend
> Starting program: E:\cvs_home\emacs23\emacs\src/.\emacs.exe
> --disable-font-backe
> nd
> [New thread 1032.0xb0c]
> [New thread 1032.0x17a8]
> [New thread 1032.0x1668]
> 
> Program exited normally.

Same question here.

> (gdb) xbacktrace
> Cannot access memory at address 0x82f6d4

This is expected: the program already exited, so its memory is no
longer accessible (it was returned to the host OS).

> (gdb) r --disable-font-backend
> Starting program: E:\cvs_home\emacs23\emacs\src/.\emacs.exe
> --disable-font-backe
> nd
> [New thread 5804.0xf84]
> [New thread 5804.0x14e8]
> [New thread 5804.0x1254]
> [New thread 5804.0xf00]
> [New thread 5804.0x1a4]
> [Switching to thread 5804.0x1a4]
> Quit (expect signal SIGINT when the program is resumed)

Doesn't happen for me.

Btw, how come your emacs.exe is in src/ directory? did you copy it
there?




  reply	other threads:[~2008-05-07 18:15 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-07 17:59 23.0.60; emacs hangs on WinXP with --disable-font-backend, and backtrace Kyle M. Lee
2008-05-07 18:15 ` Eli Zaretskii [this message]
2008-05-08  0:59   ` Kyle M. Lee
2008-05-08 10:22     ` Eli Zaretskii
2008-05-08 15:28       ` Kyle M. Lee
2008-05-08 15:37         ` Eli Zaretskii
2008-05-08 15:56           ` Kyle M. Lee
2008-05-08 16:57             ` Eli Zaretskii
2008-05-09  1:05               ` Kyle M. Lee
2008-05-09  7:22                 ` Eli Zaretskii
2008-05-09 15:20                   ` Kyle M. Lee
2008-05-09 21:46                     ` Eli Zaretskii
2008-05-10  8:56                     ` 23.0.60; emacs hangs on LoseXP " Richard M Stallman
2008-05-10 13:42                       ` Kyle M. Lee
2008-05-11  7:34                         ` Richard M Stallman
2008-05-11 12:38                           ` David Kastrup
2008-05-10 20:32                       ` David Kastrup
2008-05-08 16:03         ` 23.0.60; emacs hangs on WinXP " Kyle M. Lee
2008-05-08 11:50 ` Jason Rumney
2008-05-08 11:59   ` David Kastrup
2008-05-08 12:08     ` Jason Rumney
2008-05-08 15:40       ` Kyle M. Lee
2008-05-08 15:34   ` Kyle M. Lee

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=uk5i6dlqa.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=mail2kyle@gmail.com \
    /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).