From:	steveg AT cirris DOT com (Steve Goodrich)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Remote Debugging - dpmi exceptions
Date:	Tue, 30 Nov 99 16:29:43 GMT
Organization:	Cirris Systems Corp.
Lines:	21
Message-ID:	<820u2k$jd7$1@news.aros.net>
NNTP-Posting-Host:	cirris.cirris.com
X-Trace:	news.aros.net 943979412 19879 207.173.20.12 (30 Nov 1999 16:30:12 GMT)
X-Complaints-To:	news AT aros DOT net
NNTP-Posting-Date:	30 Nov 1999 16:30:12 GMT
X-Newsreader:	Pan 0.6.4
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

I am trying to use the i386-stub.c remote serial debugging stub with djgpp to set up remote debugging. The place I am running into problems is the callback "exceptionHandler". The stub uses this to register handlers for exeptions. One of these exceptions is the software trap used for break points.

I am makeing the assumption that I should be registering these through the dpmi services. The problem is, when I make the call to register the new handler, it fails (__dpmi_set_extended_exception_handler_vector_pm returns a -1). Here is what the code looks like:

void exceptionHandler (int exception_number, void *exception_address)
{
	__dpmi_paddr my_handler;
 	my_handler.offset32 = (int)exception_address;
	my_handler.selector = _go32_my_cs();
	int i = __dpmi_set_extended_exception_handler_vector_pm(exception_number, &my_handler);
	
}

This is my best guess as to what this code should look like after consulting the dpmi refernce on the djgpp web page.

Has anyone used remote serial debugging with djgpp? 

Am I even in the ball park on this whole exception handling registration thing?

Thanks
Steve

- Raw text -