26 Mar 2024 |
x64dbgbot | <elvis6356> it seldom happen in newer versions. But in older versions it happen alot | 04:12:36 |
x64dbgbot | <elvis6356> there is an issue on github. Idk it if related or not | 04:15:58 |
x64dbgbot | <elvis6356> https://github.com/x64dbg/x64dbg/issues/3196 | 04:15:59 |
x64dbgbot | <niku144> what does this one mean? | 06:51:42 |
x64dbgbot | Download file_1967.jpg | 06:51:43 |
x64dbgbot | <mrexodia> I’m using x64dbg a lot and cannot trigger this issue, like ever (re @elvis6356: https://github.com/x64dbg/x64dbg/issues/3196) | 09:34:52 |
x64dbgbot | <mrexodia> It would help if you could find more details on when it happens, anything interesting about your configuration? | 09:35:33 |
x64dbgbot | <elvis6356> It's weird. My configuration is almost default. I only change x64dbg's theme. I know that "could not reproduce issue" is one of the hardest issue. Anything I can help? | 09:54:28 |
x64dbgbot | <mrexodia> Generally you do not want to do things this way. What are you actually trying to do on a high level? Because you want to get at least closer to your goal in the code before tracing (re @mordaur: how would one set a breakpoint when RDX contains a certain value? from what i've found one needs to do a trace over, and set a break condition? would the syntax "rdx == 00000000FFFFFFFF" be okay for this, so that the execution breaks when RDX contains "00000000FFFFFFFF"? or am i way off here?) | 09:54:52 |
x64dbgbot | <mrexodia> Yeah, what’s your configuration? (re @elvis6356: It's weird. My configuration is almost default. I only change x64dbg's theme. I know that "could not reproduce issue" is one of the hardest issue. Anything I can help?) | 09:55:09 |
x64dbgbot | <mrexodia> I’m on windows 10 (bare metal) and amd64 | 09:55:24 |
x64dbgbot | <mrexodia> Something like this could happen if SetThreadContext fails, I think this will just silently run the executable | 09:56:14 |
x64dbgbot | <elvis6356> Yep. Check your dm | 10:02:38 |
x64dbgbot | <mordaur> nevermind. The target was a UPX compressed DLL. Was able to find the OEP, (jmp) after it unpacks itself into memory. The point was to get closer to the OEP, or break in the main code. But I figured it out. Thanks for the info though. it was indeed not the right approach. (re @mrexodia: Generally you do not want to do things this way. What are you actually trying to do on a high level? Because you want to get at least closer to your goal in the code before tracing) | 17:50:04 |
27 Mar 2024 |
x64dbgbot | <labracadabrad0r> https://n1ght-w0lf.github.io/tutorials/writing-x64dbg-plugins/ | 08:42:27 |
x64dbgbot | <labracadabrad0r> can anyone tell me how do install this plugin? | 08:42:39 |
x64dbgbot | <labracadabrad0r> can anyone tell me how to install this plugin? | 08:43:05 |
x64dbgbot | <sleekz> I mean it kinda explains it... | 09:28:16 |
x64dbgbot | <mrfearless> https://github.com/plasma-umass/ChatDBG | 12:55:08 |
x64dbgbot | <mrfearless> looks interesting | 12:55:12 |
x64dbgbot | <mrfearless> wonder if x64dbg could use that | 12:55:31 |
x64dbgbot | <el_garro> Probably, if someone is in the mood of making a plugin I can provide a scraped bingai api that doesn't require a silly api key, and doesn't look like a mess like the one in github (re @mrfearless: wonder if x64dbg could use that) | 18:38:11 |
28 Mar 2024 |
x64dbgbot | <Gsm Moz> Hi, can anybody help me, the software I'm trying to debugger is protected by VMProtect, I used to bypass it using sharpOD, but earlier this month the program was updated and now is not bypassing | 09:19:45 |
x64dbgbot | Download file_1968.jpg | 09:19:46 |
x64dbgbot | <himflc> Use Titanhide or HyperHide (re @Gsm Moz: Hi, can anybody help me, the software I'm trying to debugger is protected by VMProtect, I used to bypass it using sharpOD, but earlier this month the program was updated and now is not bypassing) | 09:38:57 |
x64dbgbot | <Gsm Moz> Thanks, I'll try now (re @himflc: Use Titanhide or HyperHide) | 09:39:31 |
x64dbgbot | <lyxfitg> yo | 10:09:28 |
x64dbgbot | <lyxfitg> i need help | 10:09:31 |
x64dbgbot | <lyxfitg> with crck some | 10:09:37 |
| MoKe joined the room. | 11:55:26 |