update: gdb logging enable/disable command

[mtwoz]

'set logging on/off' is deprecated and replaced with 'set logging enabled on/off'.

Description

• My code follows the code style of this project.
• My change includes a change to the documentation, if required.
• If my change adds new code, adequate tests have been added.
• I have read and agree to the CONTRIBUTING document.

[github-actions]

🤖 Coverage update for 1930e8d 🟢

	Old	New
Commit	92f45ba	1930e8d
Score	71.5835%	71.5835% (0)

[hugsy]

Do you happen to know in which version this deprecation occured?

Update: it seems to have appeared somewhere between v9 (doesn't work) and v12 (works).
So just to ensure retro-compatibility, please update your PR by checking the version against GDB_VERSION

[mtwoz]

Do you happen to know in which version this deprecation occured?

Update: it seems to have appeared somewhere between v9 (doesn't work) and v12 (works). So just to ensure retro-compatibility, please update your PR by checking the version against GDB_VERSION

Thanks for reminding me. So do I need to add an if judgment to choose to use 'set logging on/off' or 'set logging enabled on/off' based on GDB_VERSION?

[hugsy]

Thanks for reminding me. So do I need to add an if judgment to choose to use 'set logging on/off' or 'set logging enabled on/off' based on GDB_VERSION?

From the docs it seems that set logging enabled on/off' is the way going forward so yes, it is better to simply add a if GDB_VERSION >check until our base version supported becomes one whereset logging enabled on/off` always works