🚀 go-pugleaf

I discovered my problem. I walked the processes first
looking for my applications name and then walked the 
modules using the PID. When I walked the modules I found
that the MODULEENTRY32 structure contained what I wanted.

"Arthur Jelsma" <jelsma@wapa.gov> wrote:
>
>On a Windows 2000 machine with BCB5 Pro, I am trying to walk
>the heap of my application. I use the following API call to
>snapshot the heap:
>
>hdlSnp = CreateToolhelp32Snapshot( TH32CS_SNAPHEAPLIST, 0 )
>
>I then use Heap32ListFirst, Heap32First, Heap32Next, and 
>Heap32ListNext to walk the heap. However, I am seeing address
>data from HEAPENTRY32 which is not consistant with the memory
>display of PrcView (v3.7.3.1) for my application. I use 0 in
>CreateToolhelp32Snapshot to force it to use the current process.
>Any ideas as to what I may be doing wrong? Note the memory
>display from PrcView is consistent with addresses I am seeing
>in my application. Thanks for any help and insight that you
>can give me.
>