Ghidra1

> This problem is really weird and hard to reproduce. After testing again and again, I found that sometimes the refType is `READ_WRITE`, and sometimes it is `WRITE`. @xian-wen what...

I am unable to reproduce your READ_WRITE result for the [npp.6.2.3.Installer.exe](https://notepad-plus-plus.org/downloads/v6.2.3/) locations specified above. Mine returns WRITE.

@xian-wen Very very weird. If I iterate over all instructions using `currentProgram.getListing().getInstructions(true)` and use your logic above I am able to reproduce your results. If instead, I spot check (which...

It is also worth pointing out that auto-analysis on the entire program does not leverage the methods `getOperandRefType` or the underlying method `SleighInstructionPrototype.cacheDefaultOperandRefTypes`.

While we need to investigate the resolve logic for types pulled from archives, a work around would be to drag the type from the archive onto the type it is...

I believe this relates to an open issue previously identified internally (GP-1307): DataTypeManagerDB does not currently perform proper conflict handling when the type being resolved has a source (resolveDataTypeWithSource) when...

Could you please provide a binary which exhibits this behavior

It is possible that the section symbol is not picking up the address of the corresponding section block. Will need to investigate with a sample.

>> This binary is built to load at 0x0 Have you tried just changing the base import address to 0 instead of excepting the forced default (e.b., 0x10000) ? That...

We do sometime struggle with pre-linked relocateable binaries - could this be one of those? The relocations are present but do not need to be applied. In those cases disabling...