Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!linus!philabs!sunrise!ursa!sdo
From: sdo@ursa.UUCP
Newsgroups: comp.unix.wizards
Subject: Re: Problem with dbx on Sun3.1 (no executable code at line ...)
Message-ID: <258@teddy.ursa.UUCP>
Date: Mon, 4-May-87 12:17:47 EDT
Article-I.D.: teddy.258
Posted: Mon May  4 12:17:47 1987
Date-Received: Thu, 7-May-87 03:12:13 EDT
References: <2652@phri.UUCP>
Reply-To: sdo@teddy.UUCP (Scott Oaks)
Organization: Bear Stearns, New York
Lines: 34

In article <2652@phri.UUCP> roy@phri.UUCP (Roy Smith) writes:
>
>        On our sun-3's running Sun3.1, we sometimes have dbx refuse to set
>a breakpont at a given line, complaining "no executable code at line ..."
>when there certainly *is* code there.  For example:

This is most likely caused by the inclusion of executable code from a header
file (this at least is one way in which it is caused, though of course there
might be others).  For example:

----file defs.h------
#include <stdio.h>

#define TRUE (1)
#define FALSE (0)

#ifndef lint
static char *defssccsid = "%W% INCLUDE FILE %G%";
#endif

----------source file----------------
#include "defs.h"

main()
etc.

What happens is that the line control information produced by 3.[01] of cpp
is incorrect, so that you can't set breakpoints where you think you ought to
be able to.  This bug is fixed in 3.2.
-- 
Scott Oaks
Bear Stearns
(212) 952-3164
{convex, sunrise, cuctr}!ursa!sdo