|Re: [hatari-devel] Debugger features ideas/wishes|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel <hatari-devel@xxxxxxxxxxxxxxxxxxx>
- Subject: Re: [hatari-devel] Debugger features ideas/wishes
- From: David Savinkoff <dsavnkff@xxxxxxxxx>
- Date: Mon, 6 Sep 2021 02:11:46 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telus.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :content-transfer-encoding; bh=wwqI6heOeYUvrl0EgKN1kGXABxSdRMKFZqPwLMRItFc=; b=Yr2MAce2U5jMbEW9MJQWogKXjZDXqpS75Xnu5fEQsysoTaKF7IZl/F8T9J370RKuLH 5gHxAWCt+feHLcXh6CHlOOSlaZQR+BZaprb47RQRtWYQMzPuH2ChgFfrF9gHgMAxIjVi FoWwSzTUH5nQFUiuSUVlRm9atVjxurO51uTE0LOEFb2zcIEVrCqYPUP7xWpwItvE3Ped yklwRdqBMBMNWBz6T874WMYIVFs3mVXyxxwtOVMpoSqMw5SDr20caH7rXAqd4LnptBuC mrEW+1LQCitAZcztzqCfg43n86NRTiZeYzpwLdPUZ/ol8U4a1IObIXNerRxdJ2Kvm17S Fa7Q==
I remember a disassmembler monitor for the C=64 that would highlight
the (address of the line) you wanted to disassemble (and keep it highlighted)
so that you could scroll back and forth (disassembling).That way You
could act as a backtracking descent assembly parser to determine
if the code before the break makes sense, and determine a correct negative
Another method could be to have a side-by-side disassembler-monitor for
easy comparing and code moving (2 open windows on modern computers).
On Sun, Sep 5, 2021 at 11:54 PM Miro Kropáček <miro.kropacek@xxxxxxxxx> wrote:
> On Mon, 6 Sept 2021 at 01:46, Eero Tamminen <oak@xxxxxxxxxxxxxx> wrote:
>> Would using 'history' command help?
> Not really. For instance, consider code:
> moveq #32-1,d7 ; default init
> <some functionality>
> some_label: ; d7 initialised elsewhere
> dbra d7,some_loop
> so if something jumps to "some_label", I always have to scroll up to see what kind of loop it is (one can argue that further stepping will bring me there but that is also not always the case plus I would miss the default initialiser completely). "history" wont help either. I really need to see what's around that instruction to make sense of the whole loop.
>> One problem is some instructions have different
>> sizes, so disassembly output is potentially wrong
>> in the beginning when it's started from fixed
>> negative PC offset.