nxgdb/irq: add irqinfo command

[XuNeo]

Note: Please adhere to Contributing Guidelines.

Summary

Similar to nsh command, irqinfo shows the registered IRQ callbacks and arguements.
Arguements is shown as a function when possible.
If intrumentation is enabled, it also prints the IRQ count etc.

(gdb) irqinfo
IRQ  COUNT      TIME   RATE   HANDLER                                          ARGUMENT
0    0          0      N/A    mps_reserved                             0x0 <sensor_unregister>
2    0          0      N/A    mps_nmi                                  0x0 <sensor_unregister>
3    0          0      N/A    arm_hardfault                            0x0 <sensor_unregister>
4    0          0      N/A    arm_memfault                             0x0 <sensor_unregister>
5    0          0      N/A    arm_busfault                             0x0 <sensor_unregister>
6    0          0      N/A    arm_usagefault                           0x0 <sensor_unregister>
11   1          0      N/A    arm_svcall                               0x0 <sensor_unregister>
12   0          0      N/A    arm_dbgmonitor                           0x0 <up_debugpoint_remove>
14   0          0      N/A    mps_pendsv                               0x0 <up_debugpoint_remove>
15   6581421    0      N/A    systick_interrupt                        0x100010c <g_systick_lower>
49   2          0      N/A    uart_cmsdk_tx_interrupt                  0x1000010 <g_uart0port>
50   0          0      N/A    uart_cmsdk_rx_interrupt                  0x1000010 <g_uart0port>
59   2          0      N/A    uart_cmsdk_ov_interrupt                  0x1000010 <g_uart0port>
(gdb)

Impact

New feature.

Testing

Tested with qemu live debugging.

[nuttxpr]

[Experimental Bot, please feedback here]

Yes, this PR appears to mostly meet the NuttX requirements, but could be improved. Here's a breakdown:

Strengths:

• Clear Summary: The summary explains the purpose, functionality, and how it works. The example output is very helpful.
• Impact Section Mostly Addressed: The impact section is started, and the new feature is identified.
• Testing Evidence Provided: Testing information, including the platform and method (qemu/gdb) is present. This is good.

Weaknesses and Areas for Improvement:

• Incomplete Impact Assessment: While the "new feature" is mentioned, all other impact fields are left blank with "NO" or unanswered. Even if there's no impact, explicitly stating "NO" and briefly explaining why is helpful (e.g., "Impact on build: NO - This change only affects the gdb stub and does not modify the build system."). This demonstrates that the impact has been considered.
• Missing "Before" and "After" Logs: The testing section includes placeholders for logs but doesn't provide actual logs. This makes it difficult to verify the change's effectiveness. Show the irqinfo output before your change and after your change.
• Missing Build Host Details: Be more specific about your build host. "Linux" isn't enough. Include the distribution (e.g., "Ubuntu 22.04"), the compiler version (e.g., "gcc 11.3.0"), and any other relevant details.
• Missing Target Details: Be more specific about your target. "qemu" is a good start, but what architecture? (e.g., "qemu-system-arm"). Which board configuration? This is essential for reproducibility.
• Consider User Impact: Even though it's a debugging command, consider if there is any user impact. For example, does it consume more memory? Does it introduce any potential performance overhead, even if negligible?

Recommendation:

To fully meet the requirements, fill in the missing details in the Impact and Testing sections. Provide concrete "before" and "after" logs demonstrating the change's functionality. Be as specific as possible about your build and target environments. Even if the answer is "NO" for most impact items, provide a brief justification. This makes the PR review much easier and increases the likelihood of it being accepted.

[jerpelea]

please add commit description

[linguini1]

Could you add some information about this to the documentation website? Maybe here?

[XuNeo]

please add commit description

Done

Could you add some information about this to the documentation website? Maybe here?

Done, added to GDB with Python with a new table of commands. Currently only includes irqinfo.

[XuNeo]

Hi @jerpelea ,

Please help to review the PR again. Thank you!