Re: [Rubycocoa-talk] Where does stdout go?

[Allison N. <dem...@ma...>]

If you're running from the commad line, have you tried simply sending stdout to a file by adding '> temp_file.txt' to the end of the command line?
 
On Friday, May 23, 2008, at 02:07AM, "Pierce T. Wetter III" <pi...@tw...> wrote:
>Or really, how do I redirect it?
>
>
>  Why:
>
>   So when I'm debugging my rubycocoa app, I always launch it from the  
>command line because the ruby backtrace is my most useful debugging  
>tool.
>
>   Recently, I intergrated someone elses crash reporting tool, but so  
>far, the crash reports aren't useful because they always look like this:
>
>0   libobjc.A.dylib                	0x90a59380 objc_msgSend + 16
>1   com.apple.rubycocoa            	0x0004545b rbobj_call_ruby + 1844
>2   com.apple.rubycocoa            	0x000446b0 install_ovmix_hooks +  
>5630
>3   com.apple.rubycocoa            	0x00042bc2  
>ovmix_register_ruby_method + 2472
>4   com.apple.Foundation           	0x927f1468 - 
>[NSObject(NSForwardInvocation) forward::] + 469
>
>That is, they're objective-C backtraces.
>
>So what I'd like to do is basically startup my app with stdout  
>redirected to a file in /tmp, and then if the app crashes, I can have  
>the crashreporter email that (currently it sends console.log, which  
>isn't very useful).
>
>  How can I do that easily?
>
>  Pierce
>
>-------------------------------------------------------------------------
>This SF.net email is sponsored by: Microsoft
>Defy all challenges. Microsoft(R) Visual Studio 2008.
>http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
>_______________________________________________
>Rubycocoa-talk mailing list
>Rub...@li...
>https://lists.sourceforge.net/lists/listinfo/rubycocoa-talk
>
>