home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.pascal
- Path: sparky!uunet!mcsun!sunic!sics.se!keisu
- From: keisu@sics.se (Torbj|rn Keisu)
- Subject: BP7 - inclusion of debug information ??
- Message-ID: <KEISU.92Dec18084901@lludd.sics.se>
- Sender: news@sics.se
- Organization: Swedish Institute of Computer Science, Kista
- Date: Fri, 18 Dec 1992 07:49:01 GMT
- Lines: 27
-
- Could anyone shed some light on whats get included when the /v switch is used
- with bpc.
-
- I made a small test using a program and a single unit containing almost nothing.
-
- The following results were obtained regarding the size of the resulting .exe
-
- compile flags in pgm/unit /v flag size
- D+, L+ off 1664
- D+, L+ on 3657
- D-, L- off 1664
- D-, L- on 3569 ?????
-
- In the last line the resulting file is almost as big as the one with full debug
- info, why is this ? The difference in size compared to the /v case corresponds
- roughly to the amount of declarations and linenumbers in the program.
-
- The connection to the real world is that I have a fairly large application that
- cannot be compiled with /v flag (using bpc) even though all files have D-,L- set.
- bpc fails with error 110, which incidentally isn't in the written documentation.
- The cause is debug symbol table overflow. All is fine when compiling in the IDE
- for the internal debugger, compiling in the IDE for standalone debugging fails as
- well.
-
- Suggestions anyone ??
-
- /tk
-