[Coco] MESS/Mame emubrk/LOG/BREAK?

[tim lindner]

They will never make it into mainline MAME. Out of scope.

They will always be patches.

I stopped updating my patches after Erik started posting his to github.



On Tue, Feb 13, 2018 at 10:27 AM, Michael R. Furman <n6il at ocs.net> wrote:
> Does anyone know if Erik’s LOG and BREAK made it into standard Mess/Mame or
> will I need to patch it somehow or build the older version from Erik’s fork?
>
> How about Tim’s older EMUBRK?  Is that still around?
>
> —
>
> Michael R. Furman
> Email: n6il at ocs.net
> Phone: +1 (408) 480-5865
>
>
> Begin forwarded message:
>
> From: tlindner at macmess.org (tim lindner)
> Subject: Re: [Coco] Assembly help
> Date: October 17, 2015 at 10:59:27 AM PDT
> To: coco at maltedmedia.com ('CoCoList for Color Computer Enthusiasts')
> Reply-To: CoCoList for Color Computer Enthusiasts <coco at maltedmedia.com>
>
> Chad H <chadbh74 at hotmail.com> wrote:
>
> I WISH there was a way to do a step by step trace in assembly
> the way one can do in Microsoft's .NET languages to see exactly
> what's going on with each instruction and the variable values, etc.
>
>
> Erik Gavriluk has a fork of MAME (MESS) that includes a bunch of extras
> to help with debugging. Specifically tailored to the CoCo drivers.
>
> https://github.com/milliluk
>
> It pretty much supercedes my work with EMUBRK.
>
>
>
>
> --
> tim lindner
> tlindner at macmess.org                                              Bright
>
> --
> Coco mailing list
> Coco at maltedmedia.com
> https://pairlist5.pair.net/mailman/listinfo/coco
>
>



-- 
--
tim lindner

"Proper User Policy apparently means Simon Says."