[comp.sys.apollo] GPR Problems, C Debugger

dpunjabi@isis.UUCP (Dinesh Punjabi) (07/02/88)

Greetings !!
	I've recently started using an Apollo system ( SR9.7 & Graphics
	GPR package ). I 've run into problems  trying to allocate single 
	plane main memory bitmaps !! For example, the 
	gpr_$inq_bitmap_pointer routine does not return the correct 
	bitmap width (number of 16 bit words) for a single plane bitmap.

	Secondly, I've had problems trying to do a gpr_$additive_blt
	from a 1-plane bitmap to a 4-plane main memory bitmap.
	Have any of you faced similar problems ??

	Finally, is there any 'decent' run-time debugger for C under 
	AEGIS  ????  ( I mean other than 'debug' or -DBA )

	I would appreciate any feedback on these topics !

	Thanks in advance !!!

johnf@apollo.uucp (John Francis) (07/09/88)

In article <2295@isis.UUCP> dpunjabi@isis.UUCP (Dinesh Punjabi) writes:
>Greetings !!
>	I've recently started using an Apollo system ( SR9.7 & Graphics
>	GPR package ). I 've run into problems  trying to allocate single 
>	plane main memory bitmaps !! For example, the 
>	gpr_$inq_bitmap_pointer routine does not return the correct 
>	bitmap width (number of 16 bit words) for a single plane bitmap.

Well, actually it *does* return the correct bitmap width - it's just not
the width you might expect.  Small main memory bitmaps are always allocated
with a stride of 64 16-bit words between scanlines, even though the bitmap
may not require that much.  This is because the blitter logic in one of the
earlier monochrome machines (I believe it was the DN300) could only handle
a stride of 64 words (64 x 16 = 1024, which is the size of the frame buffer).
The board could do DMA transfers, however, so it made sense to allocate any
small main memory bitmap with a stride of 64. The extra space is not always
wasted - if you allocate another main memory bitmap GPR will try to 'fill in'
the unused space.

>	Secondly, I've had problems trying to do a gpr_$additive_blt
>	from a 1-plane bitmap to a 4-plane main memory bitmap.
>	Have any of you faced similar problems ??

As far as I know this works - it certainly did the last time I tried it!
What particular problems are you having?  I can't give you any more help
unless you describe the problem in more detail.

>	Finally, is there any 'decent' run-time debugger for C under 
>	AEGIS  ????  ( I mean other than 'debug' or -DBA )

Define 'decent'  -  debug isn't that bad! What features do you want that
debug does not offer?  However - wait until you see the SR10 debugger!!

>	I would appreciate any feedback on these topics !
>
>	Thanks in advance !!!

You're welcome.