Problems with edebug-set-conditional-breakpoint.

[Matt Hodges]

In GNU Emacs 21.3.50.3 (i686-pc-linux-gnu, GTK+ Version 2.4.13)
 of 2004-11-23 on dugong
Distributor `The XFree86 Project, Inc', version 11.0.40300001
configured using `configure '--with-gtk''

Important settings:
  value of $LC_ALL: nil
  value of $LC_COLLATE: nil
  value of $LC_CTYPE: nil
  value of $LC_MESSAGES: nil
  value of $LC_MONETARY: nil
  value of $LC_NUMERIC: nil
  value of $LC_TIME: nil
  value of $LANG: nil
  locale-coding-system: nil
  default-enable-multibyte-characters: t

I've been reading through lispref/edebug.texi and have come across two
related problems with edebug-set-conditional-breakpoint.

The first:

(1) Instrument the following for debugging:

    (defun fac (n)
      (if (< 0 n)
          (* n (fac (1- n)))
        1))

(2) Eval (fac 5) and set a conditional breakpoint on the first stop
    point [I used (eq n 3)].

(3) Trying to change the conditional breakpoint using x then M-p leads
    to an error:

        Debugger entered--Lisp error: (wrong-type-argument char-or-string-p (eq 
n 3))
          apply(debug error (wrong-type-argument char-or-string-p (eq n 3)))
          edebug(error (wrong-type-argument char-or-string-p (eq n 3)))
          next-history-element(-1)
          previous-history-element(1)

The second:

(1) As above.

(2) As above.

(3) Change the conditional breakpoint (without using the history) to
    (eq n 4).

(4) The value of read-expression-history is now:

        ("(eq n 4)"
         (eq n 3)
         "(eq n 3)")

    and the non-string element leads the following error with M-: M-p M-p

        (wrong-type-argument char-or-string-p (eq n 3))

Thanks,

Matt