On Apr 29, 2010, at 12:31 PM, Tao Wang wrote: > On Fri, Apr 30, 2010 at 3:49 AM, Clint Redwood <[email protected]> wrote: >> Hi, >> >> I'm trying to develop a gnucash (2.2.9) report on OSX, and I've so far done >> it without any error messages other than >> "Report error >> An error occurred while running the report." >> which is perhaps the least helpful message since "Segmentation fault - core >> dumped". >> >> I'm now stuck and have no idea what the report is unhappy about. >> >> I've looked at the web pages regarding trace files, but I can't find any >> such files in my OSX environment, even with the unix shell. >> >> Could someone point me in the right direction? >> > I'm not using OSX, so I'm not sure how, there are some basic links: > > http://wiki.gnucash.org/wiki/Stack_Trace > http://wiki.gnucash.org/wiki/Tracefile > > The "gnucash.trace.*" should be saved at current user's temp > directory. In MacOSX, it should be /tmp > And you can also launch GnuCash from console, so there are more stuff > will show on the console. > During my translation, I found there is a "--logto" parameters you can > use to direct the log, should follow by the filename, and can also be > "stderr" or "stdout" which will print on the console by default. >
On OSX, gnucash.trace file goes to /var/tmp. Yes, it's not the best place, but it's one that's guaranteed to be there. Error messages from a Finder-launched app go to the "console messages" logging database, which is most easily read by /Applications/Utilities/Console.app. Regards, John Ralls _______________________________________________ gnucash-devel mailing list [email protected] https://lists.gnucash.org/mailman/listinfo/gnucash-devel
