From:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: gdb error
Date:	6 Jun 2001 11:44:41 GMT
Organization:	Aachen University of Technology (RWTH)
Lines:	46
Message-ID:	<9fl539$ljq$1@nets3.rz.RWTH-Aachen.DE>
References:	<slrn9hnp2h DOT 3vv8egp DOT shankara AT shankar DOT littonas DOT com> <9fic2a$p6g$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <2950-Tue05Jun2001205536+0300-eliz AT is DOT elta DOT co DOT il> <9fj6tq$gc0$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <3791-Tue05Jun2001221850+0300-eliz AT is DOT elta DOT co DOT il>
NNTP-Posting-Host:	acp3bf.physik.rwth-aachen.de
X-Trace:	nets3.rz.RWTH-Aachen.DE 991827881 22138 137.226.32.75 (6 Jun 2001 11:44:41 GMT)
X-Complaints-To:	abuse AT rwth-aachen DOT de
NNTP-Posting-Date:	6 Jun 2001 11:44:41 GMT
Originator:	broeker@
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> wrote:
>> From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
>> Newsgroups: comp.os.msdos.djgpp
>> Date: 5 Jun 2001 18:03:38 GMT
>> 
>> > But there was never a need to mention any source files.
>> 
>> "preproc.c" in this case is not an argument for gdb. It's a command
>> line argument to be passed to the debuggee, cxref.

> This cannot be done at all with GDB, not only the DJGPP port.

Not with current GDB, sure.  All I wrote above is really just one
possible explanation about what the original poster may have had in
mind, and how he might have come to expect that to work. Some people
are still used to amazingly old version of DJGPP, it seems.

To put this all into context, here's the background story:

Back in the days of 'go32 -d gdb debuggee', the debugger was started
in a wildly different way.  It wasn't a separate program, but rather
an extension module to the go32 driver.  The debuggee was started by
go32, only to be interrupted very soon afterwards to pass control to
the debugger module.  

And as far as I remember, the way to pass command line arguments to
the debuggee indeed was to put them on the "go32 ..."  command line,
so they would be available to go32 and be passed to the debuggee even
before GDB took control.  GDB's "run" command wasn't functional, back
then, so you couldn't use the usual "run arg1 arg2" or "set args arg1
arg2" commands from inside GDB.  To start the debuggee from scratch,
you had to quit to the shell and restart the debugger and program from
scratch. 

Thus,

	go32 -g gdb cxref preproc.c

would run "cxref preproc.c" under control of GDB, back then. And at
least my collection of tools did include a "gdb.bat" that expanded to
"go32 -g gdb %1 %2 %3 %4 %5 %6 %7 %8 %9", so calling "gdb cxref
preproc.c" would have been my usual way of running such a debugger
session.
-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -