Conversation
Edited 5 hours ago
I'm parsing the #IDA type info library and it turns out:

- Sometimes struct member names are not returned. Sometimes!
- The first struct member is at offset 94489263476241, but amazingly the second one is at 8.

Just in case you wonder why I drink...

Edit: that weird value is somewhat random too, so I suspect a memory leak
1
0
1
I think I found the magic sauce of if's, now I get Memory Error which I can debug even less than the previous errors

"The operation was successful, the patient died"
2
0
0
@pancake it seems items that I reference from Python are overwritten while I go through a generator...
1
0
0

@buherator swig? I hads lots of fun messing with it when binding the r2 apis. I ended up writing my own binding toolkit, but there are lots of bottlenecks, and then you have to choose between memory leaks or double frees. Python is awful xD thats why i ended up doing r2pipe and json serializers for everything. Faster, simpler and easier to maintain

1
1
0

@buherator

I once got a "Job failed successfully" message.

Probably on Windows…

0
0
1