Timeline for Ghidra Strings and Global Renaming Issue
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 15, 2023 at 1:09 | comment | added | jttri777 | By messing around with the memory maps, I've managed to solve the issue with the "uRAM" globals, they had been placed in a memory block that was separate to the data segment, meaning that the DS value was having no effect. Merging the blocks has now solved this issue, however I still don't seem to be able to double click on the string values in the decompilation. | |
| May 14, 2023 at 22:33 | comment | added | jttri777 | Ghidra didn't pick up the data segment correctly for this executable. I had to redefine it correctly, and then manually set the DS register value for each of the functions that require it. Setting the DS register manually seems to introduce the "uRAM" globals. | |
| May 14, 2023 at 17:52 | history | edited | jttri777 | CC BY-SA 4.0 |
added 116 characters in body
|
| May 14, 2023 at 17:37 | history | asked | jttri777 | CC BY-SA 4.0 |