On Feb 7, 2010, at 10:12 AM, Marnen Laibow-Koser wrote: > > Paul Harrington wrote: >> Ralph Shnelvar wrote: >>>> That's utterly bizarre. In what context are you getting this error? >>> >>> I, and many others, seem to randomly get this error. Right now I am >>> gettnig a lot of them as I `someprogram.exe` (backtick execution) >>> >>> Hmm .. does backtick run programs in the same address space as the ruby >>> interpreter? >>> >> >> No, backtick launches a subshell to run the command... > > Is that true on Windows too?
Why would that not be true? Windows is a multitasking OS. >>> I'm curious as to why this error is not being logged. >> >> Well what *are* you shelling out? What is the full stacktrace Ruby is >> giving you? This is a key question. A different, but probably equally illuminating one to the OP is: Can you reduce this to a simple test case that others can reproduce? If so, we can read your code. Whatever the answer is, it's not jumping out at anyone except to give you the literal interpretation of the error message. Are you really doing backtick execution from within a Rails app? Do you know that will completely block the app's execution in its current process until it's done? That's undesirable at best. Again, hard to answer these questions without more context. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
