dlizewski opened a new issue, #18474:
URL: https://github.com/apache/nuttx/issues/18474

   ### Description / Steps to reproduce the issue
   
   nuttx aware debugging using tools/pynuttx/gdbinit.py was broken in 
https://github.com/apache/nuttx/pull/18221
   
   The PR claimed it was only used by the single function, but it was used by 
tools/pynuttx/nxgdb/thread.py
   
   "info threads" can no longer access g_statenames
   
   Steps to reproduce:
   1. Launch GDB with nuttx aware debugging "gdb-multiarch nuttx 
-ix=tools/pynuttx/gdbinit.py"
   2. Execute "info threads"
   
   ```
   (gdb) info threads
   Traceback (most recent call last):
     File 
"/home/daniellizewski/revisioned/nuttx/tools/pynuttx/nxgdb/thread.py", line 
219, in invoke
       statenames = gdb.parse_and_eval("g_statenames")
   gdb.error: No symbol "g_statenames" in current context.
   Error occurred in Python: No symbol "g_statenames" in current context.
   (gdb) info nxthreads
   Traceback (most recent call last):
     File 
"/home/daniellizewski/revisioned/nuttx/tools/pynuttx/nxgdb/thread.py", line 
219, in invoke
       statenames = gdb.parse_and_eval("g_statenames")
   gdb.error: No symbol "g_statenames" in current context.
   Error occurred in Python: No symbol "g_statenames" in current context.
   ```
   
   Reverting https://github.com/apache/nuttx/pull/18221 locally solved the 
problem.
   
   
   ### On which OS does this issue occur?
   
   [OS: Linux]
   
   ### What is the version of your OS?
   
   Ubuntu 22.04
   
   ### NuttX Version
   
   master
   
   ### Issue Architecture
   
   [Arch: all]
   
   ### Issue Area
   
   [Area: Other]
   
   ### Host information
   
   _No response_
   
   ### Verification
   
   - [x] I have verified before submitting the report.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to