2009/2/23 Erich Hoover <[email protected]>: > On Sun, Feb 22, 2009 at 2:34 PM, Jérôme Gardou <[email protected]> > wrote: >> >> Chris Robinson a écrit : >>> >>> Having the information there of why it crashed would be nice too, >>> especially if it's hard to reproduce. Knowing what the fault was, and where >>> (with a backtrace if possible) can give the more development-inclined people >>> information of where to look for the issue, instead of needlessly trying to >>> make it crash again or go digging around in log files. >>> >>> >> >> Well, that was the intent of my patch : ReportFault is made to give >> windows developers information about why the application catched an >> exception. There is no reason why wine people could not use it. By the way, >> is there an easy way to know if wine was launched from console or not? > > Wine may have a macro or function to check for you, but I am not aware of > it. In any application you can check to see if getenv("TERM") is empty, if > it has a value then the application was launched from a console.
#include <unistd.h> and use isatty() would be the correct way to do it. But is a dialog box that only appears when not being run from a terminal really such a good idea?
