<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
x64dbgbot
@x64dbgbot
<EvilSapphire> Dang bots debugging other programs now? They're evolving Morty!
x64dbgbot
@x64dbgbot
<Matti> oh I legit read zero of the context
<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
x64dbgbot
@x64dbgbot
<mrfearless> should charge the amount of bitcoin it would cost to buy the product for #2797 - lol
<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
x64dbgbot
@x64dbgbot
<exploit1337> It's possible to get dump automatically after virtualalloc to save time ?
x64dbgbot
@x64dbgbot
<exploit1337> Or similar script to archive this
x64dbgbot
@x64dbgbot
<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