Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 13:15
    AppVeyorBot commented #2771
  • 12:55
    ZehMatt synchronize #2771
  • 12:54
    ZehMatt synchronize #2771
  • 11:55
    mrexodia commented #2770
  • 11:54

    mrexodia on development

    fix #2769 Merge pull request #2770 from t… (compare)

  • 11:54
    mrexodia closed #2770
  • 11:54
    mrexodia closed #2769
  • 11:54
    mrexodia edited #2770
  • 11:54
    mrexodia commented #2768
  • 11:54

    mrexodia on development

    minor enhancement Merge pull request #2768 from t… (compare)

  • 11:54
    mrexodia closed #2768
  • 11:52
    mrexodia closed #2754
  • 11:52
    mrexodia labeled #2754
  • 11:51
    AppVeyorBot commented #2771
  • 11:31
    torusrxxx commented #2709
  • 11:29
    ZehMatt opened #2771
  • 11:06
    AppVeyorBot commented #2770
  • 10:47
    torusrxxx opened #2770
  • 04:00
    xtayaitak commented #2769
  • 03:16
    xtayaitak commented #2769
x64dbgbot
@x64dbgbot
<Pastor Jim Colerick> wtf
<morsisko> yeah I don't think it's because of x64dbg
<Symb0lik> cool, good to know
x64dbgbot
@x64dbgbot
<checkraisefold> if I add a log file to "trace over", it traces 1 step, logs it to the file. and finishes. if i dont use a log file, it does the full trace and saves to a .db if i use start run trace
<checkraisefold> is that a bug or?
x64dbgbot
@x64dbgbot
<mrexodia> Possibly, but I can’t reproduce it on my end (re @x64dbg_bot: <checkraisefold> is that a bug or?)
<checkraisefold> hmm.. maybe i'm doing something wrong. i set a software and hardware breakpoint (i think the hardware breakpoint doesn't get hit for some reason) at the beginning of a long function, then trace over without a log file and it works fine
<checkraisefold> but trace over with a log file selected and it only goes 1 step
<checkraisefold> very odd
x64dbgbot
@x64dbgbot
<mrexodia> Please report an issue with as much detail as possible
<mrexodia> Then I can try to reproduce it
x64dbgbot
@x64dbgbot
<dychxi> The software written in Microsoft Visual C + + 6.0 is in exe format. There is a length limit when entering the edit box. How to crack it?
x64dbgbot
@x64dbgbot
<mrfearless> @ThunderCls I came across this recently (well actually the win32metadata repo: https://github.com/microsoft/win32metadata), but noticed this repo that generates json files for win32 api: https://github.com/marlersoft/win32json
<mrfearless> I recall you mention using json for a possible rewrite of the xAnalyzer
x64dbgbot
@x64dbgbot
<TomieKawakami> my favourite plugin xD i think the most op plugin xD the xFindOut hahaha
<TomieKawakami> its like the cheat engine.. find who writes or read this address etc
x64dbgbot
@x64dbgbot
<mrfearless> and I think torus might have mentioned something similar in an issue, using some win32 api types etc, so could be useful for that if integrating directly into x64dbg
x64dbgbot
@x64dbgbot
<mrexodia> Yeah this repo is somewhere on my list because it could be used to generate types (re @mrfearless: and I think torus might have mentioned something similar in an issue, using some win32 api types etc, so could be useful for that if integrating directly into x64dbg)
<mrfearless> Yeh, the json generated files would be handy for that
x64dbgbot
@x64dbgbot
<mrexodia> Yeah
x64dbgbot
@x64dbgbot
<ThunderCls> @mrfearless that looks interesting
<mrfearless> 👍
<ThunderCls> Thanks I’ll keep it
x64dbgbot
@x64dbgbot
<SunBeam> @mrexodia got a new one for you
<SunBeam> pdb doesn't get loaded even if forced
<SunBeam> funny thing, CE does load them:
x64dbgbot
@x64dbgbot
<SunBeam> looks like IDA bitches too
x64dbgbot
@x64dbgbot
<mrexodia> 🤷🏻‍♂️ (re @x64dbg_bot: <SunBeam> pdb doesn't get loaded even if forced)
<mrexodia> I can’t do anything from the chat
<mrexodia> I will forget
<mrexodia> And it’s probably Microsoft’s fault anyway
x64dbgbot
@x64dbgbot
<SunBeam> actually
<SunBeam> it's my fault
<SunBeam> the exe/pdb don't match
<SunBeam> saw that the timestamps are different, as I can't compare by exe/pdb id
<SunBeam> back in 1998-2000, there was this trend where you'd compile a build with debug symbols, then later toggle that off
<SunBeam> so you would then have the newest exe with the pdb from 2 days ago
<SunBeam> 😄 😄
<SunBeam> of course they wouldn't match
x64dbgbot
@x64dbgbot
<mrexodia> 😄
<SunBeam> look at this:
<SunBeam> DLL from 96 with PDB from the future
<SunBeam> 😄 😄
x64dbgbot
@x64dbgbot
<SunBeam> then people ask for remakes/remastered versions and they go like "oh, gee, we don't have the source code anymore" (aka it's fucked)