From xemacs-m  Mon Jan 27 14:10:14 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
          by xemacs.org (8.8.4/8.8.4) with ESMTP
	  id OAA19749 for <xemacs-beta@xemacs.org>; Mon, 27 Jan 1997 14:10:12 -0600 (CST)
Received: by crystal.WonderWorks.COM 
	id QQcaiq11644; Mon, 27 Jan 1997 15:09:38 -0500 (EST)
Date: Mon, 27 Jan 1997 15:09:38 -0500 (EST)
Message-Id: <QQcaiq11644.199701272009@crystal.WonderWorks.COM>
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: buffer/window/frame mix-up
In-Reply-To: <199701271913.NAA19247@xemacs.org>
References: <199701271913.NAA19247@xemacs.org>

Richard Cognot writes:
 > Anyone else seeing this?
 > 
 > If I have more than one frame open, then things such as "debug on
 > error" become useless: it doesn't split the active frame to show the
 > error backtrace, but selects another frame, and never shows the
 > backtrace...

I assume you're talking about 20.0.  I don't see that behavior here.
Try to come up with a system test case using xemacs -q.

