Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 07:04
    idigger edited #2824
  • 06:56
    idigger edited #2824
  • 06:55
    idigger edited #2824
  • 06:54
    idigger edited #2824
  • 02:50
    Champollion9012 labeled #2825
  • 02:50
    Champollion9012 opened #2825
  • 00:26
    mrexodia commented #2824
  • 00:05
    mrexodia commented #2824
  • 00:03
    mrexodia commented #2824
  • 00:02
    SirHerpDerp commented #2824
  • 00:00
    SirHerpDerp commented #2824
  • Jan 21 12:30
    idigger labeled #2824
  • Jan 21 12:30
    idigger opened #2824
  • Jan 21 08:54

    torusrxxx on development

    fixed mnemonic brief not shown (compare)

  • Jan 19 00:12

    mrexodia on development

    Make all child dialogs respect … (compare)

  • Jan 19 00:04
    pka4916 commented #2801
  • Jan 19 00:02
    pka4916 opened #2823
  • Jan 19 00:02
    pka4916 labeled #2823
  • Jan 18 21:17
    SirHerpDerp commented #2821
  • Jan 18 19:56
    AppVeyorBot commented #2822
x64dbgbot
@x64dbgbot
<mrexodia> Some button in the editor might work
Torusrxxx
@torusrxxx
we need more advanced stuff in x64dbg so people who use x64dbg only don't get stuck on something professional, like Virtual Machines
Torusrxxx
@torusrxxx
I'll try to find 10 minutes to add the help messages.
To all beginners, if you find x64dbg difficult to use, tell me, I'll listen to your voice.
x64dbgbot
@x64dbgbot
<Razorrali> anybody use ss7 here ???
x64dbgbot
@x64dbgbot
<GroupAnonymousBot> ^ @Razorrali (re @mrexodia: Official x64dbg group chat.
Rules:
Torusrxxx
@torusrxxx
I just come up with an idea to create a new type of breakpoint on floating point numbers using snan
x64dbgbot
@x64dbgbot
<나쯔> Excuse me. Is x64dbg compatible with OllyDbg Script?
<mrexodia> Not really, the language is similar but not compatible
<나쯔> thk
x64dbgbot
@x64dbgbot
<Danishali123>
<Danishali123> How yo change softewere name plz help
<Danishali123> Plz
x64dbgbot
@x64dbgbot
<jvoisin> rename the .exe
x64dbgbot
@x64dbgbot
<morsisko> where in the x64dbg code the winapi message loop is implemented?
<morsisko> eg something like
while(GetMessage(&Msg, NULL, 0, 0) > 0)
{
        TranslateMessage(&Msg);
        DispatchMessage(&Msg);
}
<morsisko> because I don't see it anywhere, but the plugin`s dialog still get the messages, so I wonder how it works
x64dbgbot
@x64dbgbot
<mrexodia> Qt (re @x64dbg_bot: <morsisko> because I don't see it anywhere, but the plugin`s dialog still get the messages, so I wonder how it works)
<mrexodia> It’s in processMessage iirc
x64dbgbot
@x64dbgbot
<morsisko> naaah, don't think so
<morsisko> my question is more about the win api things
<morsisko> because normally when you, for example, create dialog in your application using CreateDialog() you need to pass the messages to the dialog with loop similar I've posted above (not sure if you messed with the winapi gui before)
<morsisko> but in case of x64dbg the loop is not needed, it look like something another is feeding the dialog queue with messages
<morsisko> not sure if it's implemented on Qt level or what, because I don't see it anywhere in the x64dbg source
<morsisko> but the message queue of my dialog is indeed filled with messages to dispatch
<mrexodia> It’s in qt
<mrexodia> But your dialog isn’t related to qt
<mrexodia> If you pump on the same thread as you created the dialog on it’ll work
<mrexodia> Or are you creating a qt dialog?
x64dbgbot
@x64dbgbot
<morsisko> Nah, I'm using the native winapi CreateDialog
<mrexodia> So then messages will be pumped by user32
<mrexodia> CreateWindow needs a loop
<mrexodia> DialogPaeamW or whatever doesn’t
<morsisko> Ah, that's the reason
<morsisko> It's kinda strange anyway, because then the "tab" key doesn't work well, but as far as I remember it worked fine with the standard dialog
<mrexodia> Hm
<mrexodia> That is weird
<morsisko> like as now you can't use tab key inside dialog without making some strange thing like subclassing inputs that are focused
<morsisko> and I see that almost every plugin for x64dbg works like this
<morsisko> (you can't use tab to switch to the next input)
<mrexodia> It could definitely be a qt issue
<morsisko> I see that with casual event loop you need to add the "IsDialogMessage" like this:
while (GetMessage(&msg, 0, 0, 0) > 0)
{
  if (!IsDialogMessage(hwnd, &msg))
  {
    TranslateMessage(&msg);
    DispatchMessage(&msg);
  }
}
<morsisko> but as the dialog got the default one, don't think there is a good way to implement this
<morsisko> but yeah that is strange, I think you can use the tab key in the native windows dialogs without any problem
x64dbgbot
@x64dbgbot
<mrfearless> Its possible to use a separate thread and then run CreateDialogParam (as an example), and use your own event loop after with the IsDialogMessage as you have above
x64dbgbot
@x64dbgbot
<morsisko> Damn this is good idea, but can i call the x64dbg from other threads in safe manner?
x64dbgbot
@x64dbgbot
<morsisko> I mean x64dbg api functions
<morsisko> Because i see this can get more complicated then
x64dbgbot
@x64dbgbot
<mrexodia> Yeah the apis should be thread safe (re @x64dbg_bot: <morsisko> Damn this is good idea, but can i call the x64dbg from other threads in safe manner?)
x64dbgbot
@x64dbgbot
<mrfearless> I did create an x64dbg plugin for auto updating, but I never released it publicly, just as a test to a few users - seemed to work mostly ok - altho there was an occasional crash if exiting x64dbg whilst that thread was active for that plugin - cant recall if i resolved that, so thats the only thing to worry about as far as i know.