[hatari-devel] register locking in debugger
Laurent Sallafranque
laurent.sallafranque at free.fr
Thu Feb 11 23:03:41 CET 2010
For me, for the dsp registers, you should only display memory+disasm for
Rx registers.
X, Y A and B registers may not point to an address area.
The same for Mx and Nx registers which are only offset registers for Rx
register
Regards
Laurent
Laurent Sallafranque a écrit :
> Hello Eero,
>
> Can you give me a little example to see what it can gives for the DSP ?
>
> Regards
>
> Laurent
>
>
> Eero Tamminen a écrit :
>
>> Hi,
>>
>> On Thursday 24 December 2009, npomarede at corp.free.fr wrote:
>>
>>
>>> But in that case, I think that adebog or monst are way more powerful than
>>> Hatari debugger, with a built in window system, register locking, search
>>> in disasm mode, ...
>>>
>>>
>> Nicolas, the infrastructure is now ready for doing register locking
>> (I added "lock" as separate command which shares code with the "info"
>> command and for conditional breakpoints there was already code for
>> handling registers).
>>
>> I was thinking of this kind of an "UI" for the register locking:
>> lock regaddr <register name>
>>
>> But what it should show when entering the debugger? Disassembly from
>> the address pointed by the "locked" register, memory dump, or both?
>> For both data and address registers?
>>
>> Laurent, what about DSP registers?
>>
>> And should this kind of setting be saved to memory state file or
>> configuration file?
>>
>>
>> - Eero
>> _______________________________________________
>> hatari-devel mailing list
>> hatari-devel at lists.berlios.de
>> https://lists.berlios.de/mailman/listinfo/hatari-devel
>>
>>
>>
>>
>
> _______________________________________________
> hatari-devel mailing list
> hatari-devel at lists.berlios.de
> https://lists.berlios.de/mailman/listinfo/hatari-devel
>
>
>
More information about the hatari-devel
mailing list