On Sep 23, 1:43 am, Milo Thurston <[EMAIL PROTECTED]>
wrote:
> Thanks - evidently I had jumped to the wrong conclusion.
> It looks like one of the object methods included in #{} within the
> system call is failing; it's strange that there's no error message but
> that must be the cause.
Sometimes exception handling code can eat useful error messages,
especially if you don't capture and display the exception object, you
may miss useful info. When diagnosing things, I occasionally find it
is useful to comment out the rescue clause and let the error bubble to
the surface. Alternatively, capture it (e.g. rescue Exception => e)
and display in your rescue clause with a logger or similar output.
-c
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
