From: "Andrew Crabtree" <andrewc AT rosemail DOT rose DOT hp DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Debugging nasm in RHIDE?
Date: Tue, 17 Feb 1998 09:33:35 -0800
Organization: Hewlett Packard
Lines: 22
Message-ID: <6cchl6$ki4$1@rosenews.rose.hp.com>
References: <34e51916 DOT 0 AT news DOT cadvision DOT com>
NNTP-Posting-Host: ros51675cra.rose.hp.com
Mime-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk


Calvin French wrote in message <34e51916 DOT 0 AT news DOT cadvision DOT com>...
>Okay, I'm having problems debugging some nasm code.
Good luck :)

> I have the most recent NASM, I think
I have 0.97.  Don't know if its the latest.

> and it appears that debug info is turned out.
Thats not possible.  Even if you have my own hacked version of nasm (which
accepts debug directives
and discards them), you don't get debug info.  Simon probably won't get to
this until summer.  I might get it working sooner if I really need it.
Don't know though.  Tips for debugging nasm code.

Use plain old gdb.
Use 'si' and 'ni' for single stepping instructions.
Use 'info reg' or 'p $reg' to print registers
Use 'display/i $eip' to get a one line moving disassembly.

Andy