Path: utzoo!attcan!uunet!zaphod.mps.ohio-state.edu!mips!wdl1.wdl.fac.com!wdl47!eric
From: eric@wdl47.wdl.fac.com (Eric Kuhnen)
Newsgroups: comp.lang.c
Subject: Re: Problem with dbx
Keywords: dbx
Message-ID: <1990Oct26.160649.7029@wdl1.wdl.fac.com>
Date: 26 Oct 90 16:06:49 GMT
References: <942@babcock.cerc.wvu.wvnet.edu>
Sender: root@wdl1.wdl.fac.com (SUPER USER)
Organization: Ford Aerospace
Lines: 30
Nntp-Posting-Host: wdl47

vrm@cathedral.cerc.wvu.wvnet.edu (Vasile R. Montan) writes:


>   I am linking with code that someone else is developing and he has
>directories organized with seperate develop and release source
>directories.  When he gets his code to a satisfactory level he places
>the library and sources in the release directory so that he can
>continue working in the develop directory without affecting me.

>   The problem is that sometimes I want to trace through his code, but
>dbx insists on using the sources in the develop directory.  I have
>tried the 'file' command to tell it to look in at the source in the
>release directory, but dbx responds with:
>warning: File `release/src/filename.c' has not been compiled with the -g option
>It then continues to use the source in the develop directory.

>   Is there a way to tell dbx to use the file anyway.  I suppose I
>could solve this problem by making him compile the code after coping
>it to the release directory, but I figure there must be a way to do
>what I want.

Unless I've missed my guess, dbx will use code that has been compiled, 
even without the -g option.  It's just that you won't be able to see the
source while you're debugging.  Now if continues to use the source in the
development directory, perhaps the development directory object code is still
being used.  I suggest recompiling the whole thing in `release/src/' yourself.
You may have to modify your "make" file to reflect the new directory,
assuming that you are using "make" in the first place.

"Q"