[glob2-devel] need new way to turn off logging (was: still getting same crashes)

[Joe Wells]

Joe Wells <address@hidden> writes:

> "Bradley Arsenault" <address@hidden> writes:
>
>>     • Bug:  Whenever I quit a game, I get a crash with this message:
>>
>>         glob2: libgag/include/StreamBackend.h:66: virtual void 
>> GAGCore::FileStreamBackend::write(const void*, size_t): Assertion `fp' 
>> failed.
>>         ORDER_PLAYER_QUIT_GAME
>
>> I can't, as hard as I try, reproduce this bug. Exactly how are you
>> quitting the game? This must be a permissions error on behalf of the
>> OS or something else.
>
> Thanks for the feedback.  Because you could not reproduce it, I have
> looked into it some more.  Your suggestion that file permissions were
> involved is the answer.
>
> I have been using the bug workaround described in this message to
> avoid glob2 filling up my disk with log files:
>
>   http://lists.nongnu.org/archive/html/glob2-devel/2007-04/msg00368.html
>
> The workaround is to turn off all permissions on my ~/.glob2/logs
> directory.  It seems that you have made some change which means doing
> that now causes a crash.  Before it used to prevent log files (and
> also cause all log messages to be sent to the standard output
> instead).
>
> For further background on why I came to this solution, you can consult
> these earlier e-mails:
>
>   http://lists.nongnu.org/archive/html/glob2-devel/2007-04/msg00341.html
>   http://lists.nongnu.org/archive/html/glob2-devel/2007-04/msg00343.html
>   http://lists.nongnu.org/archive/html/glob2-devel/2007-04/msg00348.html
>   http://lists.nongnu.org/archive/html/glob2-devel/2007-04/msg00350.html
>   http://lists.nongnu.org/archive/html/glob2-devel/2007-04/msg00362.html
>
> So either I need turning off permissions on ~/.glob2/logs to work
> again, or I need some other solution to stop glob2 from filling up my
> disk with log files.  This is important because all sorts of other
> programs start failing when the disk is filled up.

Some more information on this.  It seems that maybe a new log file
named “userCPU.log” gets created at quit time.  Unlike the other log
files if this log file can not be created then glob2 aborts.  Can
glob2 please handle this new log file like the others so that it
doesn't abort if it can't create it?

Otherwise I need some official way to get glob2 to stop making log
files (and filling up my disk with them).

-- 
Thanks,

Joe