home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!Germany.EU.net!rrz.uni-koeln.de!news.rrz.uni-koeln.de!sr
- From: sr@ph-cip.uni-koeln.de (Stefan Reisner)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: DICE & enforcer
- Date: 9 Nov 92 15:12:09
- Organization: Institute of Theoretical Physics, University of Cologne, F. R.
- Germany
- Lines: 16
- Distribution: world
- Message-ID: <SR.92Nov9151209@sun.ph-cip.uni-koeln.de>
- References: <Douglas_Stockman.1a52@grace.UUCP>
- NNTP-Posting-Host: sun.ph-cip.uni-koeln.de
- In-reply-to: Douglas_Stockman@grace.UUCP's message of 4 Nov 92 08:27:36 EST
-
- A general way to trace enforcer hunk offset information back into the
- source involves using the `dis' disassembler (appeared on a Fish disk
- some time ago). To get compatible output you must use `absolute' mode
- (i.e. addresses are hunk-relative, not label-relative).
-
- dis is aware of symbolic debugger information hunks in the executable.
- If you leave them in (there must be a linker option for that), it will
- intersperse the disassembly listing with the function and variable
- names. That way, you can at least trace the enforcer hit back into the
- offending function. By giving a closer look to the assembly instructions
- you will even be able to identify the source statement.
-
- Hope that helps.
-
- Best regards,
- Stefan Reisner (sr@ph-cip.uni-koeln.de)
-