Vladimir Panteleev

Thank you for the clarification. ~~Could you please post the executable file?~~ Oops, I see it's also included in src.zip, thank you

Okay, I had a look at this and I think it's just that the Very Sleepy UI is a little misleading. The debug information is OK. `llvm-dwarfdump` says: ```c 0x0001bf0a:...

There is nothing in the information that Very Sleepy collects that is intrinsically tied to the *start* of a function. Hypothetically, Very Sleepy could request the debug information engine to...

> I'm also done with the Command Line feature in the process selection list(#116), but it will be pushed as a separated PR. OK, then I guess you did not...

Sorry, I don't know how to help you here, except for two things: 1. The build works in AppVeyor, I'm not sure but maybe it would be worth trying to...

I understand that this only applies when selecting the process and threads to profile, and not during actual profiling (or viewing the results), right? If there is indeed a performance...

> Here are two most hungry functions (collected from thread list updates with `i2pd.exe` process opened): This looks reasonable to me, symbol resolution is bound to be the most complicated...

I don't think so, but PRs welcome!

Yes, here is the entry point for parsing command line arguments: https://github.com/mojomojomojo/verysleepy/blob/a804ae7f8ce41fc0a4e3170ad395fa2f4b26fb86/src/wxProfilerGUI/profilergui.cpp#L701 However, the export logic is in the "second half" (the result viewing window, `mainwin.cpp`), so implementing this feature...

Sorry, I'm afraid I can't help you there. I agree that it's a mess, but it's mainly Microsoft's fault. My only advice would be to try to reproduce the environment...