dumpbin output
CodeGuru Home VC++ / MFC / C++ .NET / C# Visual Basic VB Forums Developer.com
Results 1 to 4 of 4

Thread: dumpbin output

  1. #1
    John E is offline Elite Member Power Poster
    Join Date
    Apr 2001
    Location
    Manchester, England
    Posts
    4,262

    dumpbin output

    When I run dumpbin to list the exported functions from a DLL I get this output:-

    Microsoft (R) COFF/PE Dumper Version 8.00.50727.762
    Copyright (C) Microsoft Corporation. All rights reserved.


    Dump of file libgthread-2.0-0D.dll

    File Type: DLL

    Section contains the following exports for libgthread-2.0-0D.dll

    00000000 characteristics
    50BF436E time date stamp Wed Dec 05 12:51:58 2012
    0.00 version
    1 ordinal base
    2 number of functions
    2 number of names

    ordinal hint RVA name

    1 0 00001005 g_thread_init
    2 1 0000100A g_thread_init_with_errorcheck_mutexes

    Summary

    1000 .data
    1000 .idata
    2000 .rdata
    1000 .reloc
    1000 .rsrc
    4000 .text
    At least, that's the output I get when I run dumpbin in Windows 7. But if I run the same version of dumpbin in Windows XP (on exactly the same DLL) I mysteriously get some extra information:-

    Microsoft (R) COFF/PE Dumper Version 8.00.50727.762
    Copyright (C) Microsoft Corporation. All rights reserved.


    Dump of file libgthread-2.0-0D.dll

    File Type: DLL

    Section contains the following exports for libgthread-2.0-0D.dll

    00000000 characteristics
    50BF436E time date stamp Wed Dec 05 12:51:58 2012
    0.00 version
    1 ordinal base
    2 number of functions
    2 number of names

    ordinal hint RVA name

    1 0 00001005 g_thread_init = @ILT+0(_g_thread_init)
    2 1 0000100A g_thread_init_with_errorcheck_mutexes = @ILT+5(_g_thread_init_with_errorcheck_mutexes)

    Summary

    1000 .data
    1000 .idata
    2000 .rdata
    1000 .reloc
    1000 .rsrc
    4000 .text
    I've never noticed that extra info before (the sections beginning = @ILT+). Is it anything to be worried about??
    Last edited by John E; December 5th, 2012 at 08:18 AM.
    "A problem well stated is a problem half solved. - Charles F. Kettering

  2. #2
    Join Date
    Nov 2003
    Posts
    1,825

    Re: dumpbin output

    I found this reference suggesting that it has to do with intermediate linking.

    The XP vs 7 difference is interesting.

    gg

  3. #3
    John E is offline Elite Member Power Poster
    Join Date
    Apr 2001
    Location
    Manchester, England
    Posts
    4,262

    Re: dumpbin output

    Thanks Codeplug, you're right. Now that I checked a bit deeper I noticed that I only see this with my Debug DLLs. Traditionally, I've always built my Debug builds with incremental linking turned on and my Release builds with it turned off.

    I'm not sure if there's a pattern here - but I only tend to see it if I check the file on the same system it was created on. So if the file was created on Win7 and I run dumpbin from WinXP, I don't see the extra info (and vice versa).

    Strange....
    "A problem well stated is a problem half solved. - Charles F. Kettering

  4. #4
    Join Date
    Nov 2003
    Posts
    1,825

    Re: dumpbin output

    Perhaps the difference is that dumpbin has access to the PDB on your dev machine - as this seems to suggest: http://msdn.microsoft.com/en-us/libr...f(VS.100).aspx

    gg

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Windows Mobile Development Center


Click Here to Expand Forum to Full Width

This is a CodeGuru survey question.


Featured


HTML5 Development Center