emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: emacs crash


From: Dhruva Krishnamurthy
Subject: Re: emacs crash
Date: Thu, 4 Nov 2004 18:38:51 +0530

Hello,
 Now, this problem has encroached emacs-unicode-2 branch too. With the
automatic sync, which IMO has happened today, we have the same problem
(which leaves me with no working emacs).

-dhruva

On Thu, 04 Nov 2004 13:52:04 +0100, B. Anyos <address@hidden> wrote:
> 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
> > address@hidden
> > http://lists.gnu.org/mailman/listinfo/emacs-devel
> >
> >
> 
> _______________________________________________
> Emacs-devel mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/emacs-devel
> 


-- 
Proud FSF member: #1935
http://schemer.fateback.com/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]