PyGhidra: KeyError exceptions during debugger inspection

[gec1-dev]

I'm not sure this is a ghidra bug or my wrong setup. I'm trying to write a simple pyGhidra script to clean my disassembled code. I setup a Ghidra (12.0.1) environment with debugging environment using Eclipse (2025-12), PyDev (13.1.0). I'm using python version 3.14.2. However when stepping through the code in Eclipse my console gets cluttered with errors like:

10.83s - Unexpected error, recovered safely.
Traceback (most recent call last):
  File "C:\Users\myusername\.p2\pool\plugins\org.python.pydev.core_13.1.0.202509210817\pysrc\_pydevd_bundle\pydevd_xml.py", line 297, in frame_vars_to_xml
    v = frame_f_locals[k]
        ~~~~~~~~~~~~~~^^^
  File "C:\Users\myusername\AppData\Roaming\ghidra\ghidra_12.0.1_PUBLIC\venv\Lib\site-packages\pyghidra\script.py", line 183, in __missing__
    raise KeyError(k)
KeyError: 'potentialPropertiesFileLocations'

The script continues, but my print statements are lost somehow, once these errors start appearing.
There are other attributes giving the same errors, like propertiesFile or referencePrimary - none of which I use in the script - which for test purposes is very simple:

#TODO write a description for this script
#@author 
#@category _NEW_
#@keybinding 
#@menupath 
#@toolbar 
#@runtime PyGhidra


#TODO Add User Code Here

import sys

print(f"Hello world from python in ghidra")

print(f"Python version is {sys.version}")

My investigation results so far are that for the "missing" attributes - there are setter methods, like public void setPotentialPropertiesFileLocations in ghidra\app\script\GhidraScript.java but there are no getters (or a standard way to retrieve their values).

Is there a way to get rid of these exceptions?

[ryanmkurtz]

Did you use the GhidraDev eclipse plugin to create your project and to launch Ghidra?

[gec1-dev]

The script was created in Ghidra. Then I opened it in Eclipse from ghidra, closed it, and started ghidra by "Debug As > pyGhidra". Right now I have created another script with similar source within Eclipse (GhidraDev > New > GhidraScript>), even created new Ghidra Script project with the same result. The debugging session correctly stops at breakpoints, variables can be seen, just these exceptions. I already worked it around by not reporting KeyError exceptions in pydev_log in pydevd_xml.py code but I think the Ghidra code could be updated to provide getters for settable attributes - or this is PyDev bug - not judging ;-).

[ryanmkurtz]

Ok, i'll try to reproduce.