🚀 go-pugleaf

Uday S Reddy <uDOTsDOTreddy@cs.bham.ac.uk> writes:

> blueman wrote:
> I don't know how to tell the version of cygwin. I often run cygwin
> setup and it updates whatever it wants to.  I seem to have run it last
> on Dec 25.  My setup.exe is dated Jul 13, 2009 and my cygwin1.dll has
> the date of Jun 12, 2008.

Sounds like Cygwin 1.5
You can see the version by running "uname -r"

>
> --
>
> In any case, I might have made some progress in diagnosing the
> problem.  I got an inkling that the size of the message being piped
> was a factor.  So, I sorted by mbox by size and did a binary
> search. For a message of size 61682 bytes, it worked.  For size 63940,
> it hung.  So, it looks like 64K minus some delta hangs.  It could be
> some buffering issue.
>
> I also tried piping multiple small messages.
>
> - Three message sized 32, 33, 45: worked.
> - Four messages sized 32, 33, 45, 53: hung.
> - Three messages sized 33, 45, 53: hung
> - Two messages sized 45, 53: worked.
> - Three messages sized 53, 67, 68: worked.
> - Four messages sized 53, 67, 68, 72: hung.
>
> I don't see a pattern here.
>
> Good luck finding the problem.  Asynchronous problems are really hard
> to debug!

Especially hard if I can't reproduce the error (I was wrong before about
having an error under my cygwin version -- I was giving it a
non-existant target directory). I even tried it on an older version of
Emacs with Cygwin 1.5. 

(Note I am assuming you are just running the command |s on multiple
marked messages without any exit handler etc. for now)

If you are interested in debugging (which I would understand if you are
not...), I would offer the following since I can't reproduce it yet...

1. First if you can try it on Linux so hopefully we can narrow down that
   this is just a problem for you on cygwin.

2. Why don't you run ededbud-eval-top-level-form on the function
   vm-pipe-messages-to-command to see where it crashes?


3. Alternatively, you could try to do something like the following manually
   (by evaling each of the following sexp one at a time) First fill a
   buffer with >64K of stuff. Then run sequentially:

(start-process "test" "tempbuff" shell-file-name shell-command-switch "cat > testfile"))
(process-send-region process (point-min) (point-max))
(process-send-region process (point-min) (point-max))
(process-send-region process (point-min) (point-max))
(process-send-region process (point-min) (point-max))
(process-send-region process (point-min) (point-max))
; etc. repeat and seen when/whether crashes
; also check in another window whether the file testfile is getting its data
; when/if you are convinced this is working fine, continue with the
; following code:
(process-send-eof process)
(while (eq 'run (process-status process))
   	(accept-process-output process)
       	(sit-for 0))


4. Try running in emacs -q mode with vm.el loaded manually to make sure
   none of your other settings are getting in the way. Similarly, if
   running emacs from cygwin-bash, then use a default .bashrc/.bash-profile.

5. Be as explicit as possible about *everything* you are doing. Emacs
   version, cygwin version. Exact command you are running

6. Make up a non-private folder of emails that it crashes on and send it
   to me to make sure I am not running on the exact same content.

Again, if you think this is just an issue that is particular to your
setup and you are not interested in debugging, that is OK too -- since I
have it working on multiple machines and setups here so I am reasonably
confident that the vm code itself is ok.