These were my options: I noticed that some local variables do have names, but most lack them. Maybe this info is not included in the dwarf to save space?
hesopesomeso
Mine is a bit different...
pegperegogaucho
Does it emit them for you?
hesopesomeso
I had to manually set the "preload all DIEs" otherwise it would process the DWARF.
hesopesomeso
It's still doing its thing
pegperegogaucho
Keep me updated, hopefully the names are not included because I really don't want to analzye again
pegperegogaucho
That took like two hours
hesopesomeso
I can't tell if those are IDA generated names or from the debug file
hesopesomeso
but I don't think there are any
hesopesomeso
im still waiting for ghidra though ida took like a minute or two
hesopesomeso
Ghidra done, and no local var names.
hesopesomeso
Events are called Messages?..... MessageProc(...) windows, leave me alone im working with K, not you
pegperegogaucho
Yes, we have realized this some time ago. Adrien came up with events, because that seemed like the logical term, but when we inspected the CKMsgAction class of XXL1, which contains (what we called events then) messages, we learned that we were wrong
pegperegogaucho
Oh, actually the "Events" come from the CKSrvEvent, which contains the Event sequences so the individual ones were events... but in reality it contained messages as part of the event sequences...
hesopesomeso
I call them class events 🤷♂️
pegperegogaucho
Looks like the intern made this class
hesopesomeso
What's annoying about this, is that flags (CBitArray, sometimes u8) don't actually point to anything, and you just have to find the appropriate enum
pegperegogaucho
Well, nothing you can do about that
pegperegogaucho
I don't think figuring out the enum if it exists is a big deal, but of course it could just be macros which is not the right way to code
hesopesomeso
yeah, but once you do figure it out, you can set the enum as the type (+ change the width if needed)