Re: [hatari-devel] Logging prefixes

["Roger Burrows" <anodyne@xxxxxxxxxxxx>]

On 7 May 2018 at 0:44, Eero Tamminen wrote:
> 
> On 05/07/2018 12:26 AM, Roger Burrows wrote:
> > What I'm really hoping for in the next release is fewer messages during
> startup
> > (I know this was discussed earlier).  I think most users don't want or need
> to
> > see most of the messages that appear in the current release.  I count 37
> lines
> > output by Hatari during startup; the only ones I care about are:
> >   . Hatari version
> >   . options (CPU, FPU etc)
> >   . mount of hard drive image
> >   . GEMDOS HDD emulation mapping
> > So IMO nearly 90% of startup messages are useless (& annoying actually) to
> the
> > average user.
> 
> Try the Mercurial version.  Currently it gives following by default
> on EmuTOS boot:
> $ hatari --tos etos512k.img  hd/
> ---------------------------------
> INFO: Hatari v2.1.0, compiled on:  May  6 2018, 20:19:18
> INFO: GEMDOS HDD emulation, C: <-> 
> /home/eero/work/hatari/build-gcc/debugger-scripts.
> WARNING: Bus Error at address $ffff8006, PC=$e0006a addr_e3=e0006e 
> op_e3=4a78
> WARNING: Bus Error at address $ffff8282, PC=$e00156 addr_e3=e0015a 
> op_e3=4a38
> WARNING: Bus Error at address $ffff8400, PC=$e00170 addr_e3=e00174 
> op_e3=4a38
> WARNING: Bus Error at address $4fffff, PC=$e00c24 addr_e3=e00c26 op_e3=4a10
> INFO: OS clock ticks / second: 100
> WARNING: Bus Error at address $fffffa40, PC=$e00542 addr_e3=e00546 
> op_e3=4a78
> ...
> WARNING: Bus Error at address $fffffe00, PC=$e00c24 addr_e3=e00c26 
> op_e3=4a10
> WARNING: No GEMDOS dir 
> '/home/eero/work/hatari/build-gcc/debugger-scripts/AUTO'
> ---------------------------------
> 
> Above warnings are on warning level, because in some cases they
> are real issues that explain why something user tried won't
> work.  Unfortunately on boot they're rarely useful.
> 
> BUT you can now remove *all* this output with "--log-level error"
> option.
> 
Any reason that this isn't the default?  In my view, it makes more sense for 
the default to be (practically) no messages, and then, if there's a problem, 
you enable them.  Or disable them during boot only (that might be a bit tricky, 
although surely there's some heuristic that will enable Hatari to decide that 
the boot is over).

Roger