Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. General and Desktop
  4. Read/Parse PE
Forum Updated to NodeBB v4.3 + New Features

Read/Parse PE

Scheduled Pinned Locked Moved Unsolved General and Desktop
17 Posts 4 Posters 4.9k Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • B BadCoder

    Yes i know that but i need te buffer pointer for validate PE image and this buffer contains only MZ chars.

    PIMAGE_DOS_HEADER pIDH;
    PIMAGE_NT_HEADERS pINH;
    HANDLE hProcess;
     LPVOID moduleBase,stubBase;
    
            pIDH=(PIMAGE_DOS_HEADER)buffer;
            if(pIDH->e_magic!=IMAGE_DOS_SIGNATURE)
                throw QString("Invalid DOS Header found in image.");
    

    The buffer don't contains all correct char than i get invalid NT Header.

    kshegunovK Offline
    kshegunovK Offline
    kshegunov
    Moderators
    wrote on last edited by kshegunov
    #8

    @BadCoder
    Above you said that this code:

    File *file;
    fopen("C:/test.dll","w");
    fwrite(result.data(),1,result.size(),file);
    fclose(file);
    

    works as expected, which means that the buffer does contain all the needed data and there is no problem with QByteArray::data(). My guess is you're interpreting the file structure erroneously. I suggest looking up these links:
    https://msdn.microsoft.com/en-us/library/windows/desktop/ms680198(v=vs.85).aspx
    https://en.wikibooks.org/wiki/X86_Disassembly/Windows_Executable_Files#File_Format
    https://upload.wikimedia.org/wikipedia/commons/7/70/Portable_Executable_32_bit_Structure_in_SVG.svg
    http://code.cheesydesign.com/?p=572

    I'm not an expert, and this is certainly very specific for each version of windows and architecture (x86, x64) you're targeting, so the reading of the loader information table might not be at all a trivial task.

    Read and abide by the Qt Code of Conduct

    1 Reply Last reply
    0
    • B Offline
      B Offline
      BadCoder
      wrote on last edited by BadCoder
      #9

      Your linked solution is useless because i know the struct of PE (Portable Executable).
      My asnwer is another,why if i write the file dll stored in the hd contains all correct bytes else if i try to show to debug like:

      qDebug()<<result.data();
      

      this show me only the MZ chars and not all content of result array?
      Infact the IMAGE_DOS_HEADER doesn't show an error else IMAGE_NT_HEADERS yes.

      1 Reply Last reply
      0
      • jsulmJ Offline
        jsulmJ Offline
        jsulm
        Lifetime Qt Champion
        wrote on last edited by
        #10

        It's probably because QByteArray::data() returns a char*, if you print it out then the first zero byte is interpreted as string end (like c style string).

        https://forum.qt.io/topic/113070/qt-code-of-conduct

        1 Reply Last reply
        0
        • jsulmJ Offline
          jsulmJ Offline
          jsulm
          Lifetime Qt Champion
          wrote on last edited by
          #11

          What happens if you do

          qDebug()<<result;
          

          https://forum.qt.io/topic/113070/qt-code-of-conduct

          1 Reply Last reply
          0
          • B Offline
            B Offline
            BadCoder
            wrote on last edited by BadCoder
            #12
            qDebug()<<result.data();
            

            print only MZ char.
            This rappresent the bytes of a dll;
            Example of dll bytes

            Yes the problem is data result.data() return char* that contains NULL char,than my problem is how i can allocate new char* with all correct char?

            qDebug()<<result;
            

            nothings happens.Debug is empty!

            1 Reply Last reply
            0
            • jsulmJ Offline
              jsulmJ Offline
              jsulm
              Lifetime Qt Champion
              wrote on last edited by
              #13

              Why do you want to allocate new memory?
              result already contains your data.
              Did you try to do like this as I suggested above:

              qDebug()<<result;
              

              As kshegunov said you should use QByteArray::size() to get the number of bytes and not strlen() or sizeof().

              https://forum.qt.io/topic/113070/qt-code-of-conduct

              1 Reply Last reply
              0
              • B Offline
                B Offline
                BadCoder
                wrote on last edited by BadCoder
                #14

                Ok the result array contains all correct bytes and the size of it print out the correct len.
                Now i need to check if this bytes contains a valid dll image,for that i need to cast it like:

                PIMAGE_DOS_HEADER pIDH=(PIMAGE_DOS_HEADER)buffer;
                

                i can't cast QByteArray to PIMAGE_DOS_HEADER, for this motive i need char* ,
                but the result.data() contains only the MZ char when cast it.
                Infact i get valid DOS header but invalid NT Header.

                1 Reply Last reply
                0
                • jsulmJ Offline
                  jsulmJ Offline
                  jsulm
                  Lifetime Qt Champion
                  wrote on last edited by
                  #15

                  "but the result.data() contains only the MZ char when cast it" - that is wrong, the char* points to the whole content of the byte array, but this array contains zero bytes which are interpreted as end of string if you treat the char* as string. You need to parse it differently. How, depends on the content, since I do not know the structure of the content a cannot say how you should parse it.

                  https://forum.qt.io/topic/113070/qt-code-of-conduct

                  1 Reply Last reply
                  0
                  • B Offline
                    B Offline
                    BadCoder
                    wrote on last edited by
                    #16

                    Ok i fixed it!The thread can be closed!

                    1 Reply Last reply
                    0
                    • SGaistS Offline
                      SGaistS Offline
                      SGaist
                      Lifetime Qt Champion
                      wrote on last edited by
                      #17

                      You can mark the thread as solved using the "Topic Tool" button :)

                      Interested in AI ? www.idiap.ch
                      Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

                      1 Reply Last reply
                      0

                      • Login

                      • Login or register to search.
                      • First post
                        Last post
                      0
                      • Categories
                      • Recent
                      • Tags
                      • Popular
                      • Users
                      • Groups
                      • Search
                      • Get Qt Extensions
                      • Unsolved