X-Authentication-Warning:	delorie.com: mail set sender to djgpp-bounces using -f
X-Received:	by 2002:a05:6214:954:: with SMTP id dn20mr8411619qvb.122.1599231716540;
	Fri, 04 Sep 2020 08:01:56 -0700 (PDT)
X-Received:	by 2002:a25:5805:: with SMTP id m5mr9968002ybb.62.1599231716321;
	Fri, 04 Sep 2020 08:01:56 -0700 (PDT)
Newsgroups:	comp.os.msdos.djgpp
Date:	Fri, 4 Sep 2020 08:01:55 -0700 (PDT)
In-Reply-To:	<CALPW7mQS9rm=H5O-ghKwF9a=XtUDWDM8_+DT8LotZ0AFTown0w@mail.gmail.com>
Complaints-To:	groups-abuse AT google DOT com
Injection-Info:	google-groups.googlegroups.com; posting-host=176.137.64.116; posting-account=4BuJbwoAAAAIG68eUeYsXc5NjD2uAegj
NNTP-Posting-Host:	176.137.64.116
References:	<f39d7f31-8815-e9fe-7ac1-4b8551098a59 AT gmx DOT de> <20f9fc4e-bfab-c2af-38e8-c6a108555165 AT iki DOT fi>
	<693b6f14-7090-c696-4203-afc929670c0b AT gmx DOT de> <CALPW7mQS9rm=H5O-ghKwF9a=XtUDWDM8_+DT8LotZ0AFTown0w AT mail DOT gmail DOT com>
User-Agent:	G2/1.0
MIME-Version:	1.0
Message-ID:	<15faa9ee-c4e8-48d2-9a9b-d1de565cf690n@googlegroups.com>
Subject:	Re: Remote debugging
From:	"pif DOT DOT DOT AT gmail DOT com (pif0017 AT gmail DOT com) [via djgpp AT delorie DOT com]" <djgpp AT delorie DOT com>
Injection-Date:	Fri, 04 Sep 2020 15:01:56 +0000
Bytes:	3284
Lines:	37
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id 084FFGoQ009014
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

Le vendredi 4 septembre 2020 à 01:15:04 UTC+2, A. Wik (awik32 AT gmail DOT com) [via djgpp AT delorie DOT com] a écrit :
> Hi all,
> On Thu, 3 Sep 2020 at 22:55, sleep DOT  DOT  DOT  AT gmx DOT de [via dj DOT  DOT  DOT  AT delorie DOT com] 
> <dj DOT  DOT  DOT  AT delorie DOT com> wrote: 
> > 
> > "Serial debugging" was mentioned, I at first thought this would work 
> > similar, just using a serialconnection instead of ethernet. Apparently 
> > it does not work the same way as you'd debug a program via gdbserver 
> > running on a remote system. 
> > I'm not familiar with that at all. Can someone point me to an explanation? 

Gdb and gdbserver have conception problems and have quiet the same hardware requirements. Gdb teams try solve that since a long time by making them sharing more and more software but when djgpp was supported by gdb, gdbserver did not. Now, they simply drop djgpp support since version 8 or 9.

To remote or cross debug, you have to build a cross gdb that target i586-msdos-djgpp. Gdb 7.12 is okay for that. 

To debug your program running on djgpp compliant environment, you have to embedded a gdbstub. You can find one on djgpp ftp. The stub will act like gdbserver by implementing gdb communication protocol but it will be a part of your program that will catch interruption and talk to gdb at this moment.
Stubs use serial connection because it use less hardware and software that tcp/IP over ethernet. 

> > Since I am somewhat familiar with gdb and it is very common, going a 
> > route that rests on that would probably make most sense, even if it 
> > works somewhat different on DOS.

The stubs on ftp doesn't implement all gdb features. It's okay for breakpoint, stepping, read and write memory, intercepted segmentation fault. Your program have to be single threaded, multi thread is not implemented. 

S. Guillaume 

- Raw text -