Re: [hatari-devel] Hatari debug mode

[Eero Tamminen <oak@xxxxxxxxxxxxxx>]

Hi,

On 31.7.2025 18.21, Christian Zietz wrote:
> Well, I launch Hatari exclusively from the console; hence, I find this 
> separate window unbearably annoying. In particular, the separate window 
> automatically closes when Hatari quits. So, I loose all output, unless I 
> copy-paste it before quitting Hatari. In contrast, when Hatari re-uses 
> my existing console window, I can use its scroll-back buffer, long after 
> Hatari has quit. Then again, I'm tech-savvy enough to just patch the 
> required change into Hatari with a hex editor when I use a release binary.

Ok, so auto-opening console window (that closes with Hatari) is kind of 
fine for termination messages, but now for debugger invocation.

I guess only real solution for latter would be what I mentioned earlier; 
debugger shortcut (by default) invoking some simple minimal (SDL) GUI 
debugger. Unfortunately AFAIK nobody's working on something like that.


> > However, there's the Hatari use-case of redirecting Hatari trace etc
> > output to a file.  Will opening of a new console window interrupt that,
> > and completely loose rest of the output when the new window is closed at
> > Hatari exit?
>
> Right now, "hatari -W" prevents the redirection of Hatari output into a 
> file, because you freopen all the standard handles. With your recent 
> patch, this will now also happen if the user presses AltGr+Pause.

One can always specify the save files explicitly with Hatari 
"--log-file" and "--trace-file" options.  However that looses the 
ordering between the logged & traced events, and one cannot construct 
the order afterwards because Hatari does not timestamp log & trace output.

Prefixing them with timestamp similar to Linux kernel "dmesg" should be 
easy to to do.  Would that be useful?


	- Eero