setComment causes BridgeException about ghidra_bridge HOT 2 CLOSED

Hey, this is an easy fix - the BridgeException is wrapping the real exception from Ghidra, which is a NoTransactionException, so this isn't to do with ghidra_bridge at all (you'd get the same result if you did this in Ghidra's built-in python).

NoTransactionException happens because Ghidra wants you to start a "transaction" before doing anything that alters the state of the database underlying the RE (such as adding a comment). You're not the first person to hit this - see #56 (comment) for a quick example of how to solve this.

from ghidra_bridge.

@justfoxing indeed your suggestion fixed it ... before posting the issue yesterday, I checked within Ghidra and setting the comment (like in my previous post) worked, but it could also be that, once the Ghidra env is loaded, the API call to start() happens in the background (?) , anyhow, thank you!

from ghidra_bridge.