Timeline for Point-to analysis of IDA Pro
Current License: CC BY-SA 4.0
16 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 16, 2018 at 13:56 | history | bounty ended | lllllllllllll | ||
| S Oct 16, 2018 at 13:56 | history | notice removed | lllllllllllll | ||
| Oct 16, 2018 at 13:56 | vote | accept | lllllllllllll | ||
| Oct 16, 2018 at 9:00 | history | tweeted | twitter.com/StackReverseEng/status/1052122151904530432 | ||
| Oct 16, 2018 at 2:09 | answer | added | NirIzr | timeline score: 3 | |
| Oct 16, 2018 at 2:09 | history | edited | NirIzr | CC BY-SA 4.0 |
deleted 4 characters in body
|
| S Oct 15, 2018 at 12:36 | history | bounty started | lllllllllllll | ||
| S Oct 15, 2018 at 12:36 | history | notice added | lllllllllllll | Draw attention | |
| Oct 12, 2018 at 8:35 | comment | added | Anton Kukoba | neither did I, when it all stared 14 years ago :) | |
| Oct 11, 2018 at 16:41 | comment | added | lllllllllllll | @AntonKukoba. Interesting. But sometimes it is difficult to comprehend the high-level algorithm (e.g., a classic constant propagation algorithm), by just checking out the assembly code there. I didn't purchase the asm to C translator... | |
| Oct 11, 2018 at 8:44 | comment | added | Anton Kukoba | The best way to how IDA does something: use IDA to reverse IDA. I mean it. I had to reverse IDA engine a lot in order to workaround various IDA bugs, and to understand how to implement the things I see in IDC via IDA SDK. | |
| Oct 11, 2018 at 7:20 | comment | added | lllllllllllll |
wikiwand.com/en/Pointer_analysis While point-to analysis can analyze both code and data pointers, I am talking about the code pointers, pointer that point to certain functions and those functions will be indirected called
|
|
| Oct 11, 2018 at 7:19 | comment | added | lllllllllllll |
Hi @IgorSkochinsky , thanks for the note. So basically the "point-to" analysis I mentioned, tries to infer the possible value in a pointer. For instance we have a indirect call call *eax, then by somehow infer the eax could contain two possible value 0x8040204 and 0x8060208, we know how to construct the call graph edge at this call site.
|
|
| Oct 10, 2018 at 19:49 | comment | added | Igor Skochinsky♦ | what exactly is a "point-to analysis"? some definition could be useful for those unfamiliar with the term, and maybe some samples of what you mean by it being "neither sound or complete"? | |
| Oct 10, 2018 at 10:03 | comment | added | lllllllllllll | BTW: please let me know if it was more proper, to post this question in the IDA-Pro internal forum, thanks. | |
| Oct 10, 2018 at 10:02 | history | asked | lllllllllllll | CC BY-SA 4.0 |