home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.msdos.programmer
- Path: sparky!uunet!cs.utexas.edu!torn!news.ccs.queensu.ca!dmurdoch
- From: dmurdoch@QueensU.CA (Duncan Murdoch)
- Subject: Re: Easy Way To Determine STACK/HEAP Allocations In An .EXE?
- Message-ID: <Bs5J58.MvI@knot.ccs.queensu.ca>
- Sender: news@knot.ccs.queensu.ca (Netnews control)
- Organization: Queen's University, Kingston, Canada
- References: <-=nm_r_.westes@netcom.com> <Bs5HMv.MEE@knot.ccs.queensu.ca>
- Date: Wed, 29 Jul 1992 13:07:55 GMT
- Lines: 36
-
- In article <Bs5HMv.MEE@knot.ccs.queensu.ca> dmurdoch@QueensU.CA (Duncan Murdoch) writes:
- >In article <-=nm_r_.westes@netcom.com> westes@netcom.com (Will Estes) writes:
- >>Is there some easy way to determine the local stack and heap allocations
- >>in an .EXE file? To my surprise, the DOS EXEHDR utility seems to let
- >>you change these parameters in an .EXE, but it doesn't seem to give a
- >>way to determine what those values are.
-
- >Borland languages come with a program called TDUMP that'll show you the
- >.EXE header.
-
- You don't need to use TDUMP - EXEHDR will display the current header if
- you give it no options. For example,
-
- C:\TEST exehdr test
-
- Microsoft (R) EXE File Header Utility Version 2.01.003
- Copyright (C) Microsoft Corp 1985-1990. All rights reserved.
-
- .EXE size (bytes) de2
- Magic number: 5a4d
- Bytes on last page: 0190
- Pages in file: 0004
- Relocations: 0007
- Paragraphs in header: 0004
- Extra paragraphs needed: 042c
- Extra paragraphs wanted: a42c
- Initial stack location: 00a1:4000
- Word checksum: 0000
- Entry point: 0000:0000
- Relocation table address: 001c
- Memory needed: 19K
-
-
- Duncan Murdoch
- dmurdoch@mast.queensu.ca
-
-