I've been having some issues with Everything lately -- using heavy amounts of CPU, the GUI interface not responding (even though Process Monitor shows that it's still indexing alright on the backend), etc.
It seems that looking at the debugging output doesn't give enough information in some cases. Would it be possible to get the debugging symbols so that we can see functions/stackwalks?
Can we get Everything's debugging symbols?
-
- Posts: 79
- Joined: Sun Jul 13, 2014 12:20 am
Re: Can we get Everything's debugging symbols?
Thanks for the issue report.
Is there a lot of file system activity during this time?
What version of Everything are you using?
I don't usually have symbols for the nightly / beta builds.
Normally I find the offending function from just the return offset and looking at the disassembly.
Could you please give the offset of the last Everything function call?
Hope I can help.
Is there a lot of file system activity during this time?
What version of Everything are you using?
I don't usually have symbols for the nightly / beta builds.
Normally I find the offending function from just the return offset and looking at the disassembly.
Could you please give the offset of the last Everything function call?
Hope I can help.
-
- Posts: 79
- Joined: Sun Jul 13, 2014 12:20 am
Re: Can we get Everything's debugging symbols?
Good idea, I'll check file system activity the next time it happens and report back, along with the function offsets.
For reference, I'm using v.851b. But this was also happening with 809b (I was hoping the nightly would fix it).
For reference, I'm using v.851b. But this was also happening with 809b (I was hoping the nightly would fix it).