Date:	Tue, 20 Jul 1999 12:08:55 +0300 (IDT)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	marciom <marciom AT geocities DOT com>
cc:	djgpp AT delorie DOT com
Subject:	Re: Code split
In-Reply-To:	<hlwk3.1012$J5.13518@c01read02-admin.service.talkway.com>
Message-ID:	<Pine.SUN.3.91.990720120820.4115N-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 19 Jul 1999, marciom wrote:

> #include <allegro.h>
> #include "fichario.h"
> #include "dados.c"
> #include "interfac.c"
> 
> Having split the code in different files I now just can debug 
> step-by-step the code in main file "fichario.c". 
> 
> How do I put it all (maybe using a Project) in a way
> that I can debug/trace code in every file?

Others already told you that including a .c file is a bad idea.

If you really, REALY need to do that, compile your program with
-gstabs+, and then the debugger will be able to step/trace into
the included source.

This is in the FAQ, btw (section 12.8).

- Raw text -