View Single Post
Dragokas
Senior Member
Join Date: Nov 2017
Location: Ukraine
Old 10-21-2018 , 21:43   Re: Accelerator - Crash Reporting That Doesn't Suck
Reply With Quote #274

asherkin, ok this is very nice tool and web-system.

But, how to analyze them to track what plugin causes crash?

I dunno how plugins loader internals are implemented in sm.
But, is it possible e.g. to find mem. adresses of each plugins ("modules" or w/e) and track what address the crash instruction was called from in chain, and map that adress to concrete name of plugin?

Here is my case: https://crash.limetech.org/4pspcj6vl7zw
More info in crash.log: https://pastebin.com/HS6nJpHz

How my strategy should looks like, if I want to find the list of sm functions that can call "UpdateAddonBits" when they are executed ?
Code:
<CTerrorPlayer::UpdateAddonBits()+65>
Is it something like:
Code:
SetEntProp(client, Prop_Send, "m_upgradeBitVec", bits, 4);
Also, how can I see the reason of crash, like "null pointer dereference" or so (without good knowledge in asm) ?

Thank you,
Stanislav.
__________________
Expert of CMD/VBS/VB6. Malware analyst.
Dragokas is offline