ollydbg - how to keep debugged program window open












0















Any way to keep debugged program window open while stepping the code in ollydbg? The program displays buttons in a loop in a dialog box. But its window stays minimized so I can't observe what effect each command has on visual display.



source: https://legend.octopuslabs.io/sample-page.html (tutorial 16A)










share|improve this question























  • I'm afraid it is just "stuck" since you are debugging it.

    – Geno Chen
    Nov 28 '18 at 3:40











  • @Geno Chen That's what I thought, but the author posts "screenshots" of buttons being created in loop iterations and it creates an impression that it somehow should be possible; the thumbnail of the window is still available so the information is there, but how do I access it?

    – astandet
    Nov 28 '18 at 3:49













  • In my remember, you can just keep it there, don't let OlldDbg maximize to hover over this window, will let you can see it.

    – Geno Chen
    Nov 28 '18 at 4:01











  • @Geno Chen Thanks, that actually solves it. It should be marked as accepted answer but since it's a comment it doesn't seem possible. Any moderator here?

    – astandet
    Nov 28 '18 at 8:42











  • I wrote an (may be more detailed and contain some error) answer.

    – Geno Chen
    Nov 28 '18 at 8:58
















0















Any way to keep debugged program window open while stepping the code in ollydbg? The program displays buttons in a loop in a dialog box. But its window stays minimized so I can't observe what effect each command has on visual display.



source: https://legend.octopuslabs.io/sample-page.html (tutorial 16A)










share|improve this question























  • I'm afraid it is just "stuck" since you are debugging it.

    – Geno Chen
    Nov 28 '18 at 3:40











  • @Geno Chen That's what I thought, but the author posts "screenshots" of buttons being created in loop iterations and it creates an impression that it somehow should be possible; the thumbnail of the window is still available so the information is there, but how do I access it?

    – astandet
    Nov 28 '18 at 3:49













  • In my remember, you can just keep it there, don't let OlldDbg maximize to hover over this window, will let you can see it.

    – Geno Chen
    Nov 28 '18 at 4:01











  • @Geno Chen Thanks, that actually solves it. It should be marked as accepted answer but since it's a comment it doesn't seem possible. Any moderator here?

    – astandet
    Nov 28 '18 at 8:42











  • I wrote an (may be more detailed and contain some error) answer.

    – Geno Chen
    Nov 28 '18 at 8:58














0












0








0








Any way to keep debugged program window open while stepping the code in ollydbg? The program displays buttons in a loop in a dialog box. But its window stays minimized so I can't observe what effect each command has on visual display.



source: https://legend.octopuslabs.io/sample-page.html (tutorial 16A)










share|improve this question














Any way to keep debugged program window open while stepping the code in ollydbg? The program displays buttons in a loop in a dialog box. But its window stays minimized so I can't observe what effect each command has on visual display.



source: https://legend.octopuslabs.io/sample-page.html (tutorial 16A)







debugging reverse-engineering ollydbg






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 28 '18 at 3:34









astandetastandet

32




32













  • I'm afraid it is just "stuck" since you are debugging it.

    – Geno Chen
    Nov 28 '18 at 3:40











  • @Geno Chen That's what I thought, but the author posts "screenshots" of buttons being created in loop iterations and it creates an impression that it somehow should be possible; the thumbnail of the window is still available so the information is there, but how do I access it?

    – astandet
    Nov 28 '18 at 3:49













  • In my remember, you can just keep it there, don't let OlldDbg maximize to hover over this window, will let you can see it.

    – Geno Chen
    Nov 28 '18 at 4:01











  • @Geno Chen Thanks, that actually solves it. It should be marked as accepted answer but since it's a comment it doesn't seem possible. Any moderator here?

    – astandet
    Nov 28 '18 at 8:42











  • I wrote an (may be more detailed and contain some error) answer.

    – Geno Chen
    Nov 28 '18 at 8:58



















  • I'm afraid it is just "stuck" since you are debugging it.

    – Geno Chen
    Nov 28 '18 at 3:40











  • @Geno Chen That's what I thought, but the author posts "screenshots" of buttons being created in loop iterations and it creates an impression that it somehow should be possible; the thumbnail of the window is still available so the information is there, but how do I access it?

    – astandet
    Nov 28 '18 at 3:49













  • In my remember, you can just keep it there, don't let OlldDbg maximize to hover over this window, will let you can see it.

    – Geno Chen
    Nov 28 '18 at 4:01











  • @Geno Chen Thanks, that actually solves it. It should be marked as accepted answer but since it's a comment it doesn't seem possible. Any moderator here?

    – astandet
    Nov 28 '18 at 8:42











  • I wrote an (may be more detailed and contain some error) answer.

    – Geno Chen
    Nov 28 '18 at 8:58

















I'm afraid it is just "stuck" since you are debugging it.

– Geno Chen
Nov 28 '18 at 3:40





I'm afraid it is just "stuck" since you are debugging it.

– Geno Chen
Nov 28 '18 at 3:40













@Geno Chen That's what I thought, but the author posts "screenshots" of buttons being created in loop iterations and it creates an impression that it somehow should be possible; the thumbnail of the window is still available so the information is there, but how do I access it?

– astandet
Nov 28 '18 at 3:49







@Geno Chen That's what I thought, but the author posts "screenshots" of buttons being created in loop iterations and it creates an impression that it somehow should be possible; the thumbnail of the window is still available so the information is there, but how do I access it?

– astandet
Nov 28 '18 at 3:49















In my remember, you can just keep it there, don't let OlldDbg maximize to hover over this window, will let you can see it.

– Geno Chen
Nov 28 '18 at 4:01





In my remember, you can just keep it there, don't let OlldDbg maximize to hover over this window, will let you can see it.

– Geno Chen
Nov 28 '18 at 4:01













@Geno Chen Thanks, that actually solves it. It should be marked as accepted answer but since it's a comment it doesn't seem possible. Any moderator here?

– astandet
Nov 28 '18 at 8:42





@Geno Chen Thanks, that actually solves it. It should be marked as accepted answer but since it's a comment it doesn't seem possible. Any moderator here?

– astandet
Nov 28 '18 at 8:42













I wrote an (may be more detailed and contain some error) answer.

– Geno Chen
Nov 28 '18 at 8:58





I wrote an (may be more detailed and contain some error) answer.

– Geno Chen
Nov 28 '18 at 8:58












1 Answer
1






active

oldest

votes


















0














Since you are debugging this program, the program will be "stuck" before GUI components initialized and enter the main loop of GUI thread. You can just keep all window away of "hovering" the program's window, for example don't maximize your OllyDbg window.






share|improve this answer























    Your Answer






    StackExchange.ifUsing("editor", function () {
    StackExchange.using("externalEditor", function () {
    StackExchange.using("snippets", function () {
    StackExchange.snippets.init();
    });
    });
    }, "code-snippets");

    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "1"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53511717%2follydbg-how-to-keep-debugged-program-window-open%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Since you are debugging this program, the program will be "stuck" before GUI components initialized and enter the main loop of GUI thread. You can just keep all window away of "hovering" the program's window, for example don't maximize your OllyDbg window.






    share|improve this answer




























      0














      Since you are debugging this program, the program will be "stuck" before GUI components initialized and enter the main loop of GUI thread. You can just keep all window away of "hovering" the program's window, for example don't maximize your OllyDbg window.






      share|improve this answer


























        0












        0








        0







        Since you are debugging this program, the program will be "stuck" before GUI components initialized and enter the main loop of GUI thread. You can just keep all window away of "hovering" the program's window, for example don't maximize your OllyDbg window.






        share|improve this answer













        Since you are debugging this program, the program will be "stuck" before GUI components initialized and enter the main loop of GUI thread. You can just keep all window away of "hovering" the program's window, for example don't maximize your OllyDbg window.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 28 '18 at 8:57









        Geno ChenGeno Chen

        2,6626925




        2,6626925
































            draft saved

            draft discarded




















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53511717%2follydbg-how-to-keep-debugged-program-window-open%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

            Calculate evaluation metrics using cross_val_predict sklearn

            Insert data from modal to MySQL (multiple modal on website)