[hatari-devel] Debugger Question

Laurent Sallafranque laurent.sallafranque at free.fr
Mon Jan 11 23:46:04 CET 2010


I've uploaded 2 disasm_functions :

Crossbar_disasmRegisters()
Videl_disasmRegisters()

I've added the prototypes as extern in the respective .h files
Is it OK for you ?

Regards,

Laurent



Eero Tamminen a écrit :
> Hi,
>
> On Monday 11 January 2010, Laurent Sallafranque wrote:
>   
>> I'd like to add a "componet" debugging to the debugger.
>>
>> I'm starting to have a look at the Videl component, and I've written this:
>>
>> /**
>>  * VIDEL_disasmRegisters : display the Videl registers values.
>>  */
>> void VIDEL_disasmRegisters(void)
>>     
> ...
>   
>> I'd like to get the whole register values of the Videl at once with one
>> debugger command. Something like "vd" for videl disasm would be great.
>>
>> I could do the same for the crossbar (command cd for crossbar
>> disassemble ?).
>>
>> Do you think we could add this function to the debugger ?
>>     
>
> I was thinking of adding an "info" function to the debugger which could
> provide this kind of information.  We could then have:
> 	info videl
> 	info crossbar
> 	info tos
> 	info program
> etc.
>
> (These things don't need to have one or two letter acronyms because
> I can add TAB completion for them like I've done for some of the other
> debugger commands.)
>
>
> However, if the provided information is machine specific (videl is Falcon
> only etc) or OS specific (TOS vs. MiNT...), it should have appropriate
> checks and show something like:
> 	"No Videl"
> when the HW or OS is not running.
>
> If you add these kind of functions to debug/info.c file:
> 	void Info_Videl(void)
> I can do the integration & TAB completion.
>
>
> 	- Eero
>
>
>   




More information about the hatari-devel mailing list