Here's another Darcs failure.

This is on Windows with darcs 1.0.9, using ssh.  The local repo is not partial.  I was pulling from the main GHC repo.

As usual I'm stumped.  A subsequent 'darcs pull' said "no remote changes to pull in".  So maybe it's ok.  But the failure message is alarming

Simon

[Add some x86/Linux outputs
Ian Lynagh <igloo@earth.li>**20080603145857]
[Add x86-linux output for a couple of benchmarks running the slow way
Ian Lynagh <igloo@earth.li>**20080603164937]
diffing dir...
Applying patches to the local directories...
diffing dir...
darcs failed: 512 at ./darcs-all line 59.

No idea.  The error message is from the darcs-all script (and not darcs), but I
do not know why it would be exiting 512.

I did not find any interesting instances of the string '512' in our source code.

Thoughts, anyone?

I've no ideas.

David

It's especially weird since exit code is a single byte under POSIX. Dunno about
Windows though. Might be something else than darcs is generating that? I actually
don't know zilch about Windows, but could the 512 be a symptom of a violent
termination, by something akin to a Unix signal? Out of memory, whatever? I can't
extract any useful information from that myself. I think there's basically no way
to know what's going wrong from the report...

Does this help at all?
  http://coding.derkeiler.com/Archive/Python/comp.lang.python/2004-05/3713.html

In the sense that the exit code isn't /really/ 512?

Maybe #haskell would know what it means when we get an exit 512 from a Haskell
program?

Now, then, 512 sounds like a bug in whatever has been calling darcs. So what does
an exit code 2 mean with darcs? And is the caller bug really forgetting to shift
the value from the OS, or is it mangling it differently? (I believe applying
WEXITSTATUS under POSIX.)