<stefano9991> Thanks for your reply, I found that, but not the function implementation
<stefano9991> Thanks! (re @x64dbg_bot: <morsisko> https://github.com/x64dbg/x64dbg/blob/18b949ee51a634bf5fff3ee717a765ba136cb791/src/dbg/commands/cmd-searching.cpp#L342)
<some> anyone help me?
<some> the x32dbg is very slow but the x64 is fast
<some> and two weeks ago the x32dbg working perfectly
<some> but now
<some> nope
<ZehMatt> you need to provide more details than that in order to get help
<some> can i share the screen?
<c0rt3x0> check ur plugins
<some> Do you have a little time?
<some> https://www.mediafire.com/file/omwa2geix98u7px/x32dbg.mp4/file the size is to big so i upload to mediafire
<c0rt3x0> or is an old update?
<c0rt3x0> and then re try
<mrexodia> Is your computer extremely low end? (re @x64dbg_bot: <some> https://www.mediafire.com/file/omwa2geix98u7px/x32dbg.mp4/file the size is to big so i upload to mediafire)
<some> idk
<Matti> what with the 'idk' answers to questions like are you on the latest version combined with the URL in the profile
<Matti> discord profile* to clarify
<Matti> so maybe I'm just a moron
<Matti> but I don't see how anyone could be so lazy as to answer 'idk' to a question someone asks you because they're trying to help you
<Matti> namely is that the same version as the latest on the site
<Matti> I've had this problem before where I couldn't tell if someone was simply lazy/stupid or an actual bot
<Matti> this AI thing is getting out of hand
<mrexodia> I banned that user and deleted the issue (re @mrfearless: should charge the amount of bitcoin it would cost to buy the product for #2797 - lol)
<mrfearless> concur
<mrfearless> looks like very specialized software anyhow
<mrfearless> requiring hardware keys and licenses
<mrfearless> I imagine you could do it in a plugin, have breakpoints on VirtualAlloc - either manually or from the plugin itself perhaps. Then when breakpoint is triggered, plugin can check if it was for VirtualAlloc call, (determine length of alloc and store that) then it can single step, collect the value in eax, check its not null, then dump to file based on debuggee name + concat of "_dump"+ dumpNo for the length of the alloc
<exploit1337> Thx , the issue is that there are about 200+ calls of virtualalloc and I need at least to check them at dump view to see the headers that interests me (re @mrfearless: https://twitter.com/IntezerLabs/status/1467842258653245445?s=20)