On Thu, Jun 24, 1999 at 10:22:40AM -0400, Stefan Monnier wrote:
> Too bad you can't reproduce it any more. Do you remember if it was
> an `assert failure' by any chance ?
Now I reproduced it. There are actually two failures that occur:
1.
ctwm: otp.c:188: CheckConsistency: Assertion `((owl->type == IconWin) && (owl == twm_win->icon->otp)) || ((owl->type == WinWin) && (owl == twm_win->otp))' failed.
2.
Congratulations, you have found a bug in ctwm
If a core file was generated in your directory,
can you please try extract the stack trace,
and mail the results, and a description of what you were doing,
to Claude.Lecommandeur@epfl.ch. Thank you for your support.
...exiting ctwm now.
I case you want to know the scenario:
I have gnu emacs running with only one iconified frame, and I ran
(gnuserv-start) in .emacs.
The icon name is "emacs@SG.tau.ac.il".
When I execute "gnuclient somefile" in an xterm Emacs open a new frame
for editing. Since there are two frames now, each one get a
buffer-name as window/icon name and the first frame also pops up.
I got failure 1 when reiconifying the original frame, and failure 2
when closing the new frame. (no core dump)
> I might try to merge the autolower patch into mine (as well as upgrade to
> the latest ctwm release).
> I'll send an announcement on this list when it is done.
That would be great.
Daniel
This archive was generated by hypermail 2.1.2 : Sat Jun 22 2002 - 06:45:06 CEST