emacs-pretest-bug
[Top][All Lists]
Advanced

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

Re: Crash when visiting source file


From: Steven T. Hatton
Subject: Re: Crash when visiting source file
Date: Tue, 31 May 2005 06:35:05 -0000
User-agent: KMail/1.8

On Tuesday 31 May 2005 01:21, Eli Zaretskii wrote:
> > From: "Steven T. Hatton" <address@hidden>
> > Date: Mon, 30 May 2005 18:47:27 -0400
> >
> > The first anomaly appears at line 2146:
> >
> > #2142 0x08130380 in mark_object (arg=139610081) at
> > /download/org/gnu/emacs/emacs/src/alloc.c:5316 #2143 0x08130508 in
> > mark_object (arg=138258477) at
> > /download/org/gnu/emacs/emacs/src/alloc.c:5427 #2144 0x08130380 in
> > mark_object (arg=143049133) at
> > /download/org/gnu/emacs/emacs/src/alloc.c:5316 #2145 0x08130508 in
> > mark_object (arg=144785989) at
> > /download/org/gnu/emacs/emacs/src/alloc.c:5427 #2146 0x0813023e in
> > mark_buffer (buf=Variable "buf" is not available. ) at
> > /download/org/gnu/emacs/emacs/src/alloc.c:5484
>
> That's not an anomaly, it just means that the argument `buf' was
> optimized away by the compiler, so GDB can no longer show its value.
> This is normal and has nothing to do with the crash.
>
> This crash is inside garbage collection.  The file etc/DEBUG has
> instructions on how to debug such crashes (search for "GC").
>
> Also, please post the top of the backtrace, the one that starts with
> frame #0.


I just ran Emacs with the Enter Debugger on C-g option enabled, and was able 
to capture the attached file.  It's a Lisp backtrace.
-- 
Regards,
Steven

Attachment: backtrace
Description: Binary data


reply via email to

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