Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!decwrl!purdue!gatech!ncsuvx!mcnc!duke!helios!apte
From: apte@helios.cs.duke.edu (Jitendra Apte)
Newsgroups: comp.unix.questions
Subject: Re: dbx screwing up...
Keywords: dbx
Message-ID: <14490@duke.cs.duke.edu>
Date: 12 May 89 14:27:34 GMT
References: <1666@eric.mpr.ca>
Sender: news@duke.cs.duke.edu
Reply-To: apte@helios.UUCP (Jitendra Apte)
Organization: Blue Hell - Home of the Blue Devil
Lines: 33

In article <1666@eric.mpr.ca> parker@waters.mpr.ca (Ross Parker) writes:
>
>We have seen a bizarre problem with dbx when trying to debug a very large
>(tens of thousands of lines) application. This is Ultrix 2.2 on a
>Microvax II. The problem is that when a breakpoint is set in a particular
>function (i.e. 'stop in functionname'), the source displayed with 'list'
>is not always the first executable line of code.

I have experienced similar problems, and was wondering what the world thinks of
it.

While stepping through a program, dbx says that it is at line number
"XYZ" whereas control is actually a few lines ahead of "XYZ". It
seems to be occuring because I have some character strings in my source
code with escaped newlines in them. However, I may be wrong.

	eg :  
	{
		char * p;
		p = "This is an example of the kind of string \
I was talking about";
	}

Any ideas as to whether this problem has been noticed before and if the reason
stated above is correct? I am using dbx on a Sun4 running SunOS-3.2.

Fangs a lot.
Jitendra.


(Internet) apte@cs.duke.edu; (UUCP) {decvax|ihnp4|allegra}!duke!apte
"Let us save the kid from abortion, so that he can grow up to steal bread,
 rob banks and murder people. Then we can kill him in the electric chair".