Debugger in MSX-DOS

Page 2/2
1 |

By saccopharynx

Master (150)

saccopharynx's picture

02-10-2020, 18:04

But in that case, is it possible to set a BP, which is triggered regardless the segment, by simply clicking with the mouse on the left side of the address?

By Manuel

Ascended (16961)

Manuel's picture

02-10-2020, 18:54

Briq: how exactly did you add the breakpoint when it failed?

By Briqunullus

Master (174)

Briqunullus's picture

02-10-2020, 19:43

Well, I can't click left of the address from the Code View, cause that points to the BIOS and it has no address $100. So I use the dialog you get from Breakpoint -> Add instead.

There is probably some logic to it, but from a user point of view, the dialog has "random" preset values for slot, subslot and segment. I altered only slot and subslot for my use, so the breakpoint only got triggered once when segment accidently had the correct value.

By Manuel

Ascended (16961)

Manuel's picture

02-10-2020, 22:53

I noticed that when I input $100 in that dialog, all the other values go to 'any' automatically.

By saccopharynx

Master (150)

saccopharynx's picture

02-10-2020, 23:32

That is because just $0100 is not an address used in common by code from different slots/subslots. But I think (I'm not right now on the computer), that if you set a BP at an address used in common, by just clicking on the left of it, the parameters are not automatically set to any. If that is the case, I think they should, just to be consistent with setting BPs using the menu. In addition to that, I have just found out, thanks to this post, that such BP's parameters exist, because I have never set a BP in my life using the debugger menu.

Although the parameters make sense, you will never realise of their use by setting BPs with the mouse, which is the most intuitive approach when a debugger is not a horrendous abortion like GDB!

By pgimeno

Master (238)

pgimeno's picture

04-10-2020, 16:29

saccopharynx wrote:

That is because just $0100 is not an address used in common by code from different slots/subslots. But I think (I'm not right now on the computer), that if you set a BP at an address used in common, by just clicking on the left of it, the parameters are not automatically set to any. If that is the case, I think they should, just to be consistent with setting BPs using the menu.

I think it makes best sense to make the breakpoint only trigger for the code you see in front of you. If it triggered at the same address in a different slot or segment, I could get very confused about what is that code and why it is breaking there.

That said, it would be nice to have the ability to right click on the breakpoint to edit it.

By saccopharynx

Master (150)

saccopharynx's picture

05-10-2020, 00:57

pgimeno wrote:
saccopharynx wrote:

That is because just $0100 is not an address used in common by code from different slots/subslots. But I think (I'm not right now on the computer), that if you set a BP at an address used in common, by just clicking on the left of it, the parameters are not automatically set to any. If that is the case, I think they should, just to be consistent with setting BPs using the menu.

I think it makes best sense to make the breakpoint only trigger for the code you see in front of you. If it triggered at the same address in a different slot or segment, I could get very confused about what is that code and why it is breaking there.

That said, it would be nice to have the ability to right click on the breakpoint to edit it.

Honestly, I had no idea that those "hidden" parameters existed. So, without that knowledge or the ability to find them easily, for me, it would have been better to have the brekpoints triggered regardless the slot/subslot, by setting the paramter to "any" by default, with the ability to remove those that are triggered when the intended slot/subslot is not connected to the respective page.

Of course that your point is valid too if you think that it is confusing the other way around.

Page 2/2
1 |