[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference vaxuum::online_bookbuilding

Title:Online Bookbuilding
Notice:This conference is write-locked: see note 1.3.
Moderator:VAXUUM::UTT
Created:Fri Aug 12 1988
Last Modified:Mon Jul 15 1991
Last Successful Update:Fri Jun 06 1997
Number of topics:440
Total number of notes:2134

136.0. "Runaway in index build" by CVG::THOMPSON (Protect the guilty, punish the innocent) Mon May 22 1989 13:45

	I've got a book I'm trying to build. It builds fine with other
	destinations than Bookreader. With Bookreader I get the following
	errors in the log file. The book 'built' is unreadable by the
	bookreader.

%INX-S-CREATED, 'WORK1:[THOMPSON]CTM$REFERENCE_GUIDE_INDEX.TEX;1' created
[ T e x t    F o r m a t t i n g   I n d e x ]...
%TEX-I-INFO, loading online doctype design file, TEX$O_REFERENCE - on page [1]
%TEX-W-RUNAWAY, Runaway 'argument'
%TEX-I-SHOWTOKEN, '{ \inxentry {0}{MODIFY}{}\inxentry {1}{ENTRY}{\hbox {243}\inxrefsep \ETC.'
%TEX-W-EOP, Paragraph ended before the following completed:
-TEX-W-DURING, Error occurred during a '\inxentry'
-TEX-W-MISSINGRBRACE, Possible missing '}'
%TEX-I-SHOWCONTEXT, '                   \par '
%TEX-I-LINE, Error occurred on or around line number: 122
%TEX-I-FILENAME, 'WORK1:[THOMPSON]CTM$REFERENCE_GUIDE_INDEX.TEX;1'
-TEX-I-ONPAGE, on page [1] 

%TEX-I-PAGESOUT, 2 pages written.

	I took a look in the .TEX file and few lines before the line 122
	pointed to in the log is the following line. Nothing like it
	shows up in the .TEX for the PS output versions.

\inxentry{0}{^^M}{\hbox{16}}%

	Any clues? What does anyone need to figure out what is causing
	this?

		Alfred
T.RTitleUserPersonal
Name
DateLines
136.1VAXUUM::UTTMon May 22 1989 17:238
    I would be glad to look at the book, but if it's a long book please
    try to pare it down to a reasonably small SDML file that reproduces
    the error. (Try processing each chapter separately til you find
    the one that causes the error and MAIL me that file.)
    
    Thanks,
    
    Mary
136.2pressing onCVG::THOMPSONProtect the guilty, punish the innocentWed May 24 1989 13:4650
    Well it's sort of a long book (I think. How long is long?). Anyway
    I set off to pare it down and went all the way. Binary searches are
    a wonderful concept. I found a problem (why I say a rather than the
    is to follow). What I found was an index entry in an <example_sequence>
    that was no part of an <extext>. When I removed that the text formatting
    of the index went fine. Still not sure why the <X>(START) turned up
    in the M section of the index but that's not my problem to fix. :-)

    Now what is happening is that I get an ACCVIO during the $$drivoila.

$ $$drivoila "WORK1:[THOMPSON]CTM$REFERENCE_GUIDE.DVI_BOOKREADER;" /h=36 /v=36
%DVC-I-INCLUDING, including input file: 
   doc$local_formats:small_logo.rags
%DVC-I-INCLUDING, including input file: 
   CTM$REFERENCE_GUIDE_CONTENTS
%DVC-I-INCLUDING, including input file: 
   ctm$ref_library:ctm$design.DECW$BOOKFIG
%DVC-I-INCLUDING, including input file: 
   CTM$REFERENCE_GUIDE_INDEX
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=0001473C, PC=000108C0, PSL=03C00000

  Improperly handled condition, image exit forced.

	Signal arguments	      Stack contents

	Number = 00000005		 200BEC10
	Name   = 0000000C		 00206F74
		 00000004		 00000000
		 0001473C		 00000004
		 000108C0		 00000000
		 03C00000		 0000020B
					 0000001C
					 00000140
					 00000001
					 0000020E

	Register dump

	R0 = 00000001  R1 = 7FEFAE28  R2 = 00002711  R3 = 00002710
	R4 = 00000000  R5 = 00000000  R6 = 00000718  R7 = 00067974
	R8 = 0000AEFC  R9 = 0000ACB4  R10= 0000AEF0  R11= 7FFE2BDC
	AP = 7FEFADD0  FP = 7FEFAD90  SP = 7FEFAE0C  PC = 000108C0
	PSL= 03C00000


    	I don't what to go through a second binary search if I can avoid
    	it. My book is built 'funny' as I didn't know much about DOCUMENT
    	when I started. It has a main file and two smaller ones that
    	are included in it. I'm going to try and eliminate the two smaller
    	ones and see if the problem is in one of them or in the main file.

    	Any other hints?

    				Alfred
136.3 CLOSET::FITZELLput nifty saying hereWed May 24 1989 17:443
    send me a pointer to the DVI files and I'll take a look at it.
    
    Mike
136.4fixed in next releaseCVG::THOMPSONProtect the guilty, punish the innocentThu May 25 1989 11:554
    Fixed in a device converter coming in the near future. Thanks
    to Mike for helping me out here.
    
    			Alfred