Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. General Programming
  3. COM
  4. how do i read a Heap Dump? (look in for example)

how do i read a Heap Dump? (look in for example)

Scheduled Pinned Locked Moved COM
questionc++comhelptutorial
3 Posts 2 Posters 0 Views 1 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.
  • T Offline
    T Offline
    Tim Rymer
    wrote on last edited by
    #1

    How do I read this? does (118) mean the line? cause i've looked and it just wasnt what it would seem to be. Data: < GET > 01 00 00 00 03 00 00 00 03 00 00 00 47 45 54 00 strcore.cpp(118) : {3409} normal block at 0x0760B628, 28 bytes long. Data: < /gue> 01 00 00 00 0F 00 00 00 0F 00 00 00 2F 67 75 65 strcore.cpp(118) : {3408} normal block at 0x0760B5C0, 30 bytes long. Any help get a big Thank You! ~Timothy T. Rymer www.digipen.edu tim.xpertz.com

    D 1 Reply Last reply
    0
    • T Tim Rymer

      How do I read this? does (118) mean the line? cause i've looked and it just wasnt what it would seem to be. Data: < GET > 01 00 00 00 03 00 00 00 03 00 00 00 47 45 54 00 strcore.cpp(118) : {3409} normal block at 0x0760B628, 28 bytes long. Data: < /gue> 01 00 00 00 0F 00 00 00 0F 00 00 00 2F 67 75 65 strcore.cpp(118) : {3408} normal block at 0x0760B5C0, 30 bytes long. Any help get a big Thank You! ~Timothy T. Rymer www.digipen.edu tim.xpertz.com

      D Offline
      D Offline
      Derek Waters
      wrote on last edited by
      #2

      Is this a dump of memory leaks? If so, read on... 118 is the line in strcore.cpp where the memory-leaking block was allocated. The best way to track down these bugs (without BoundsChecker or similar) is using _crtBreakAlloc in the VC++ debugger. Search MSDN for "HOWTO: Use _crtBreakAlloc to Debug a Memory Allocation" for more info, but basically you start the debugger, set _crtBreakAlloc to equal the second number (3409 or 3408) in the lines above, and then run. When the memory that is leaking is allocated, the debugger will break and show you where. Good luck. ------------------------ Derek Waters derek@lj-oz.com

      T 1 Reply Last reply
      0
      • D Derek Waters

        Is this a dump of memory leaks? If so, read on... 118 is the line in strcore.cpp where the memory-leaking block was allocated. The best way to track down these bugs (without BoundsChecker or similar) is using _crtBreakAlloc in the VC++ debugger. Search MSDN for "HOWTO: Use _crtBreakAlloc to Debug a Memory Allocation" for more info, but basically you start the debugger, set _crtBreakAlloc to equal the second number (3409 or 3408) in the lines above, and then run. When the memory that is leaking is allocated, the debugger will break and show you where. Good luck. ------------------------ Derek Waters derek@lj-oz.com

        T Offline
        T Offline
        Tim Rymer
        wrote on last edited by
        #3

        sweet thanks i'll try it - it looks like that'll work ~Timothy T. Rymer www.digipen.edu tim.xpertz.com

        1 Reply Last reply
        0
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • World
        • Users
        • Groups