unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "B. Anyos" <banyos@freemail.hu>
Cc: chenggao@gmail.com, rms@gnu.org, Jason Rumney <jasonr@gnu.org>
Subject: Re: emacs crash
Date: Thu, 04 Nov 2004 16:48:19 +0100	[thread overview]
Message-ID: <418A4F43.2000906@freemail.hu> (raw)
In-Reply-To: <418A0512.3000901@gnu.org>

It is true, I'm running emacs on Windows. So stacktrace is stopped right in
the middle of Fx_create_frame, though it seems it is over BLOCK_INPUT.
(file w32fns.c)

Anyway I tried to do what you asked for. Here's what I could figure out.

   debug_print(args[0]):
	face-set-after-frame-default

  (struct Lisp_String *)(0xfffffff & ((struct Lisp_Symbol *) (0xfffffff & args[0]))->xname):
	size		28
	size_byte	-1
	intervals	0x00000000
	data		0x01185dd0 "face-set-after-frame-default"

I hope this helps.

Unfortunately those nice commands listed in .gdbinit do not exist on MS Windows.
Any alternatives to help debugging on Windows ?


Jason Rumney said the following on 11/4/2004 11:31 AM:
> Richard Stallman wrote:
> 
>> For instance, there is something really strange here:
>>
>>    funcall_lambda(int -2128849612, int 1, int * 0x0082f980) line 2946 
>> + 17 bytes
>>    Ffuncall(int -2147483648, int * 0x0082f980) line 2814 + 12 bytes
>>    call1(int 556794192, int -2127346688) line 2547 + 11 bytes
>>    Fx_create_frame(int 0) line 4355
>>
>> There is no call to Fx_create_frame in line 4355; in fact, line 4355
>> is far after the end of Fx_create_frame.  What's going on?
>>
> I think the user is on Windows, so that would be line 4355 of w32fns.c, 
> which is in Fx_create_frame.
> 
> My line numbers are slightly out, but I suspect this line (4350 in my 
> version):
> 
>  /* Set up faces after all frame parameters are known.  This call
>     also merges in face attributes specified for new frames.  If we
>     don't do this, the `menu' face for instance won't have the right
>     colors, and the menu bar won't appear in the specified colors for
>     new frames.  */
>  call1 (Qface_set_after_frame_default, frame);
> 
> 
> It appears to be outside the BLOCK_INPUT blocks within x_create_frame.
> 
> 
> 
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-devel
> 
> 

  parent reply	other threads:[~2004-11-04 15:48 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-03  9:55 emacs crash B. Anyos
2004-11-03 10:28 ` Jason Rumney
2004-11-03 10:50   ` B. Anyos
2004-11-03 11:21     ` Jason Rumney
2004-11-03 11:29       ` Dhruva Krishnamurthy
2004-11-03 12:02       ` B. Anyos
2004-11-03 11:06   ` Dhruva Krishnamurthy
2004-11-03 14:09     ` CHENG Gao
2004-11-03 15:02       ` B. Anyos
2004-11-04  9:51         ` Richard Stallman
2004-11-04 10:31           ` Jason Rumney
2004-11-04 12:52             ` B. Anyos
2004-11-04 13:08               ` Dhruva Krishnamurthy
2004-11-05  8:38                 ` Cheng Gao
2004-11-04 15:48             ` B. Anyos [this message]
2004-11-05  0:15               ` Richard Stallman
2004-11-04 17:05             ` Jan D.
2004-11-05  8:03               ` Stefan
2004-11-04  9:51       ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2003-10-08 12:42 Werner LEMBERG
2003-08-16 13:56 Werner LEMBERG
2003-08-18  4:52 ` 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

  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=418A4F43.2000906@freemail.hu \
    --to=banyos@freemail.hu \
    --cc=chenggao@gmail.com \
    --cc=jasonr@gnu.org \
    --cc=rms@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).