From:	Mavi Gozler <MaviGozler AT yahoo DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Problem debugging mix of C and ASM files
Date:	Tue, 01 Feb 2000 14:38:20 GMT
Organization:	Deja.com - Before you buy.
Lines:	21
Message-ID:	<876r4t$gkv$1@nnrp1.deja.com>
NNTP-Posting-Host:	195.112.142.189
X-Article-Creation-Date:	Tue Feb 01 14:38:20 2000 GMT
X-Http-User-Agent:	Mozilla/4.0 (compatible; MSIE 5.0; Windows 95; DigExt)
X-Http-Proxy:	1.1 x34.deja.com:80 (Squid/1.1.22) for client 195.112.142.189
X-MyDeja-Info:	XMYDJUIDbuyuk_yarak
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I have a program built without problems using a mix of C files (with -g
option) set and one O file, a COFF object of an ASM put together by
NASM v0.98.

My running of the program within gdb produces a SIGSEGV within the code
of the ASM file.  When I use the disassemble command to list the
function containing the address which caused the fault, the
disassembled code doesn't look anything like the code of my function
however.  Moreover (and stranger yet!!), I can exit and re-start an
instance of gdb with this executable, and the code it disassembles for
my function is completely different than in the prior instance.  It
doesn't seem to know what my function is from one run to the next.

Is there something I need to do especially when linking a mix of C and
ASM (or their objects) files?


Sent via Deja.com http://www.deja.com/
Before you buy.

- Raw text -