Re: GC bug?

[Stephen Berman]

On Mon, 24 Oct 2005 01:45:46 +0200 address@hidden (Kim F. Storm) wrote:

> Stephen Berman <address@hidden> writes:
>
>> I tried to do this.  Fgarbage_collect is called at several places in
>> the Emacs C sources, but I assume you mean the invocation in alloc.c,
>> so that's where I put the breakpoint.  When I set the breakpoint
>> before inducing the infinite loop, then gdb hits the breakpoint
>> immediately, so I cannot induce loop.  So I first induced the loop and
>> then set the breakpoint, and this is the result:

I now have a reliable recipe for inducing the infinite loop:
1. have a nonempty diary file
2. emacs -q
4. M-x calendar
5. add a new entry to the diary file and don't save the file
6. in Calendar type `d' on the date of the new, unsaved entry
=> Emacs goes into an infinite loop

This is GNU Emacs 22.0.50.24 (i686-pc-linux-gnu, GTK+ Version 2.8.3)
of 2005-10-20

> use the xbacktrace command in gdb to know what functions are
> called when the loop occurs.

Here it is:

Starting program: /home/steve/cvsroot/emacs/src/emacs -q
[Thread debugging using libthread_db enabled]
[New Thread 1084223872 (LWP 16261)]

Program received signal SIGTSTP, Stopped (user).
[Switching to Thread 1084223872 (LWP 16261)]
0x0813e4c1 in Fgarbage_collect () at alloc.c:5882
5882          if (!VECTOR_MARKED_P (vector))
(gdb) xbacktrace
"diary-list-entries"
"diary-view-entries"
"call-interactively"

Is there any other information I can provide or is this enough to
find the bug?

Steve Berman