Re: edebug doesn't always work

[Joe Corneli]

       Sometimes when I run `edebug-defun', the echo area displays
       a messages that indicated that the function has been 
       instrumented, but then edebug does not take over when the
       function is called.  

       I don't know what causes this behavior, and I'm looking for
       suggestions.  The only workaround I've found so far is to 
       restart Emacs (or to do all my debugging "by hand")!

   If you tell us how to reproduce the problem, we can debug it
   and determine the cause.

I know, but I'm currently pretty clueless about where the problem is
coming from.  Currently I can only describe it as a "random failure".
So, two (multipart) questions:

(1) Any suggestions about how to lessen the degrees of freedom?
Should I edebug `edebug-defun'?  Is there something I can do with GDB
that would help?  Is there some other good way to get edebug to output
its vital statistics?

(2) Am I the only person reporting/seeing this bug?  If there are
other people with the same "random failure" problem, maybe we can pool
our knowledge.

Of course, if I had a full transcript of everything I typed into Emacs
from startup-time to failure-time, I could send that to you (or pick
over it myself for a clue) but I fear that it would be rather
overwhelming.  Still, I guess I might try it!