From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: gdb error
Date: 5 Jun 2001 10:25:14 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 16
Message-ID: <9fic2a$p6g$1@nets3.rz.RWTH-Aachen.DE>
References: <slrn9hnp2h DOT 3vv8egp DOT shankara AT shankar DOT littonas DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 991736714 25808 137.226.32.75 (5 Jun 2001 10:25:14 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 5 Jun 2001 10:25:14 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Shankar Chakkere <shankara AT erols DOT com> wrote:

> ~/develop/cxref/cxref-1.5c > gdb cxref preproc.c

That's not the correct way of starting a gdb session on DJGPP. It used
to be that way a *long* time ago (in DJGPP versions1.12 or earlier, if
memory serves), but now, you should

	c:/your/path > gdb cxref
[...]
	(gdb) break some_function_of_your_choice
	(gdb) run preproc.c

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.