[Top][All Lists]

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

Re: Build hangs in lisp/gnus.

From: Alan Mackenzie
Subject: Re: Build hangs in lisp/gnus.
Date: Sun, 5 Apr 2015 10:54:11 +0000
User-agent: Mutt/1.5.23 (2014-03-12)

Hello, Eli.

On Sat, Apr 04, 2015 at 07:56:41PM +0300, Eli Zaretskii wrote:
> > Date: Sat, 4 Apr 2015 16:42:15 +0000
> > Cc: address@hidden
> > From: Alan Mackenzie <address@hidden>

> > Run till exit from #4  0x00000000005f5e5d in Ffuncall (nargs=3, 
> > args=0x7fff0f1dc3a8) at eval.c:2721

> > .  Does that give any useful information?

> Yes, it now becomes important to understand what was that frame
> doing.  Can you reproduce the same hang and backtrace at will?  If so,
> after you attach GDB, and assuming the frame that calls Ffuncall is
> again frame #4, type these commands:

>  (gdb) frame 4
>  (gdb) p args[0]
>  (gdb) xtype
>  (gdb) p args[1]
>  (gdb) xtype
>  (gdb) p args[2]
>  (gdb) xtype

> For each Lisp type that "xtype" reports, there's a corresponding
> command to display the Lisp object in human-readable form: "xsymbol"
> for a symbol, "xstring" for a string, "xvectorr" for a vector, etc.
> So after each "xtype" command invoke the corresponding command to
> display the object, and let's take it from there.

I've found the problem.  I'd created a new (defalias 'cl-caddr 'caddr)
whilst overlooking the existing (defalias 'caddr 'cl-caddr) in cl.el.  So
I got an alias loop.

I've written down all the gdb tips for future use.  Thanks!

Alan Mackenzie (Nuremberg, Germany).

reply via email to

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