GNU bug report logs - #844
23.0.60; ediff-merge-revision: Buffer exceeds maximum size

Previous Next

To reply to this bug, email your comments to 844 AT debbugs.gnu.org.
There is no need to reopen the bug first.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Michael Kifer <kifer <at> cs.sunysb.edu>
To: "Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com>
Cc: emacs-pretest-bug <at> gnu.org
Subject: Re: 23.0.60; ediff-merge-revision: Buffer exceeds maximum size
Date: Sun, 31 Aug 2008 18:43:54 -0400

On Sun, 31 Aug 2008 23:40:13 +0200
"Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com> wrote:

> Michael Kifer wrote:
> > 
> > On Sun, 31 Aug 2008 15:40:21 +0200
> > "Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com> wrote:
> > 
> >> When I just made a checkout of Emacs from CVS I got a merge conflict
> >> which I used ediff-revision to resolve. I then got the following back
> >> trace when I did "wb" to save the corrected file:
> >>
> >> Debugger entered--Lisp error: (error "Buffer exceeds maximum size")
> >>   call-process("diff" nil #<buffer *ediff-custom-diff*> nil "-c"
> > 
> > This says that the output of diff -c exceeds the buffer size.
> > 
> > It is unclear how this is related to ediff per se, since ediff merely calls
> > call-process with the above command.
> > 
> >> "c:/DOCUME~1/LENNAR~1/LOCALS~1/Temp/ediff282470M"
> >> "c:/ecvsnew/bld/emacs/src/w32term.c")
> >>   apply(call-process "diff" nil #<buffer *ediff-custom-diff*> nil ("-c"
> >> "c:/DOCUME~1/LENNAR~1/LOCALS~1/Temp/ediff282470M"
> >> "c:/ecvsnew/bld/emacs/src/w32term.c"))
> >>   ediff-exec-process("diff" #<buffer *ediff-custom-diff*> synchronize
> >> "-c" "c:/DOCUME~1/LENNAR~1/LOCALS~1/Temp/ediff282470M"
> >> "c:/ecvsnew/bld/emacs/src/w32term.c")
> >>   ediff-compute-custom-diffs-maybe()
> >>   ediff-save-buffer(nil)
> >>   call-interactively(ediff-save-buffer nil nil)
> >>
> >> Looking into ediff-custom-diff I can see there is some problem with ^M:
> > 
> > Can you explain what the problem is? It is unclear from the included text below.
> 
> Sorry, I thought the part of the output below should show it, but of
> course the ^M characters I saw is gone here...
> 
> Lines somewhere below the middle of the output below had extra ^M at the
> end of them.
> 
> I can't reproduce the problem now, maybe it was some kind of temporary
> problem - perhaps a bad checkin to the CVS at that time?

I don't know -haven't seen this. But the main problem seems to have been that
diff -c produced a very large buffer, although I can't imagine  how big it
could have been in order to cause the "Buffer exceeds maximum size" error.
In any case, it seems to be a problem with diff or call-process, if at
all.

> > In any case, I deed to be able to reproduce it in order to be able to determine
> > if something needs to be fixed in ediff. Right now it does not look like
> > an ediff problem.
> > 
> > michael
> > 
> > 
> >> ! 	emacs_event->part = scroll_bar_handle;
> >> ! 	y = 0;
> >> ! 	break;
> >>         case SB_BOTTOM:
> >> ! 	emacs_event->part = scroll_bar_handle;
> >> ! 	y = top_range;
> >> ! 	break;
> >>         case SB_THUMBTRACK:
> >>         case SB_THUMBPOSITION:
> >> ! 	if (VERTICAL_SCROLL_BAR_TOP_RANGE (f, XINT (bar->height)) <= 0xffff)
> >>             y = HIWORD (msg->msg.wParam);
> >>
> >> ! 	bar->dragging = Qt;
> >>
> >> ! 	emacs_event->part = scroll_bar_handle;
> >>
> >>
> >>
> >> ! 	/* "Silently" update current position.  */
> >>
> >> ! 	{
> >>
> >> ! 	  SCROLLINFO si;
> >>
> >>
> >>
> >>
> >> This was with my patched version, but I do not think I have any patches
> >> that comes in here:
> >>
> >> In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
> >>  of 2008-08-28 (patched)
> >> Windowing system distributor `Microsoft Corp.', version 5.1.2600
> >> configured using `configure --with-gcc (3.4) --cflags -Ic:/g/include'
> >>
> >>
> > 
> 

Message #12 received at 844 <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Michael Kifer <kifer <at> cs.sunysb.edu>
To: 844 <at> debbugs.gnu.org
Date: Sun, 31 Aug 2008 20:57:48 -0400

This bug is not reproducible.

Message #19 received at 844-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: "Lennart Borgman \(gmail\)" <lennart.borgman <at> gmail.com>
Cc: 844-done <at> debbugs.gnu.org
Subject: Re: 23.0.60; ediff-merge-revision: Buffer exceeds maximum size
Date: Tue, 02 Sep 2008 20:19:27 -0400

Are you able to reproduce this?

Message #35 received at 844-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: "Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com>
To: Chong Yidong <cyd <at> stupidchicken.com>
Cc: 844-done <at> debbugs.gnu.org
Subject: Re: 23.0.60; ediff-merge-revision: Buffer exceeds maximum size
Date: Wed, 03 Sep 2008 02:19:36 +0200

Chong Yidong wrote:
> Are you able to reproduce this?

No, unfortunately not. It could be some issues with resources of some
kind (since I see very strange problems sometimes when the GDI objects
gets to many), but I really do not know.

Message #36 received at 844-done <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: "Lennart Borgman \(gmail\)" <lennart.borgman <at> gmail.com>
Cc: 844-done <at> debbugs.gnu.org
Subject: Re: 23.0.60; ediff-merge-revision: Buffer exceeds maximum size
Date: Tue, 02 Sep 2008 20:25:21 -0400

"Lennart Borgman (gmail)" <lennart.borgman <at> gmail.com> writes:

> Chong Yidong wrote:
>> Are you able to reproduce this?
>
> No, unfortunately not. It could be some issues with resources of some
> kind (since I see very strange problems sometimes when the GDI objects
> gets to many), but I really do not know.

Okay.  I'm closing the bug; if you encounter the problem again, we can
re-open it.

Message #49 received at 844-quiet <at> emacsbugs.donarmstrong.com (full text, mbox):

From: Jason Rumney <jasonr <at> gnu.org>
To: Emacs bug Tracking System <control <at> debbugs.gnu.org>
Cc: 844-quiet <at> debbugs.gnu.org
Subject: previously closed unreproducible bug still there
Date: Sat, 21 Mar 2009 11:51:46 +0800

unarchive 837
reopen 837
merge 837 2706
thanks

Reopened, as bug has been reported by another user and reproduced (once) 
by a developer, though method of reproducing it is still uncertain.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.