Open astrelsky opened 2 years ago
Am pretty sure this is a known issue, but will try to find the ticket and maybe dig in to see what the underlying cause is. My recollection was this is a non-trivial problem.
Am pretty sure this is a known issue, but will try to find the ticket and maybe dig in to see what the underlying cause is. My recollection was this is a non-trivial problem.
It doesn't really seem to cause any problems but now that you mention it I think I do remember something about it
Still searching, but, if you need to, am pretty sure you can hit T and put a pointer32 there.
Still searching, but, if you need to, am pretty sure you can hit T and put a pointer32 there.
That's what I ultimately ended up doing. This is mostly an aesthetic and inconvenience problem.
You could also try <type>*32
.
So I did actually encounter a problem I think is related to this. I created a struct in the dynamic listing and when I tried to change the type of a pointer field I would get an error every time I tried to move in the dynamic listing. I'm going to attempt to reproduce it later to get some logs.
:/ I can't seem to reproduce it and unfortunately the original logs are gone with a vm snapshot restore.
@astrelsky Talked about this yesterday with @nsadeveloper789 - he was aware of the issue with struct's. Apparently, this is related to more complex issues involving the DataTypeManager, which is in the process of being modified. So, the good news is it's being worked; the bad news, of course, no current workable solution.
@astrelsky Talked about this yesterday with @nsadeveloper789 - he was aware of the issue with struct's. Apparently, this is related to more complex issues involving the DataTypeManager, which is in the process of being modified. So, the good news is it's being worked; the bad news, of course, no current workable solution.
Ok not a problem. I've only encountered it once so far.
This is still an issue, but <type>*32
still works as a fix.
To Reproduce Steps to reproduce the behavior:
Maybe it has to do with why I always see Ghidra loading the 64 bit sleigh spec or a completely different architecture in some cases when opening the debugger tool.
I'm also just now noticing the instructions are the 64 bit variant in the dynamic listing as well.