- From: Amancio Hasty <hasty@rah.star-gate.com>
- Date: Thu, 15 May 1997 04:42:37 -0700
- To: Daniel Veillard <Daniel.Veillard@imag.fr>
- cc: www-amaya@w3.org
Hi, Yes, I am using the Java version. I noticed that in init.c:LoadHTMLDocument, amaya gets a little confused with respect to determining if the cache directory is created or not. Not sure how to fix it however I would do a stat on the cache directory and if it is not there create one. The symptom is that amaya fails to display http:// urls however local files are displayed with no problems. Going back and forth with sites , I managed to get this core dump: ine 2055, char 104: Unexpected end tag </FONT> Thot tool kit error: element does not match DTD Thot tool kit error: element does not match DTD Thot tool kit error: Element has no box Program received signal SIGSEGV, Segmentation fault. 0x731d7 in TtaAddPSchema () (gdb) bt #0 0x731d7 in TtaAddPSchema () #1 0x1e77b in ParseHTMLStyleHeader (elem=0x1f1f980, attrstr=0x1753ec " BODY { background : #FFFFFF }", doc=1, rebuild=0 '\000') at /spare/toolkit/Thot/amaya/css.c:926 #2 0xf983 in TextToDocument () at /spare/toolkit/Thot/amaya/html2thot.c:1495 #3 0x12f56 in HTMLparse (infile=0x84bc830, HTMLbuf=0x0) at /spare/toolkit/Thot/amaya/html2thot.c:4312 #4 0x149b1 in StartHTMLParser (doc=1, htmlFileName=0x1ae8e28 "/root/.amaya/1/Manual.html", documentName=0x1ae9050 "Manual.html", documentDirectory=0x1ae8c28 "/root/.amaya/1/", pathURL=0x1ae9250 "http://www.w3.org/pub/WWW/Amaya/User/Manual.html") at /spare/toolkit/Thot/amaya/html2thot.c:5684 #5 0x473e in LoadHTMLDocument (doc=1, pathname=0x1ae9250 "http://www.w3.org/pub/WWW/Amaya/User/Manual.html", tempfile=0x1ae9a50 "/root/.amaya/amaya_req84", documentname=0x1ae9050 "Manual.html") at /spare/toolkit/Thot/amaya/init.c:918 #6 0x516a in GetHTMLDocument ( documentPath=0x1aef540 "http://www.w3.org/pub/WWW/Amaya/User/Manual.html", form_data=0x0, doc=1, baseDoc=1, DC_event=DC_FALSE) at /spare/toolkit/Thot/amaya/init.c:1387 #7 0x205e9 in GotoPreviousHTML (doc=1, view=1) at /spare/toolkit/Thot/amaya/HTMLhistory.c:108 #8 0x90e02 in APP_ButtonCallback () #9 0x83353d8 in XtCallCallbackList () #10 0x81c6633 in ActivateCommon () #11 0x81c64b9 in Activate () #12 0x836276b in HandleActions () #13 0x836302e in HandleComplexState () #14 0x836310b in _XtTranslateEvent () #15 0x83407ff in XtDispatchEventToWidget () #16 0x834121d in L403 () #17 0x8341453 in L458 () #18 0xa2115 in TtaHandleOneEvent () #19 0x2b133 in JavaHandleOneEvent () #20 0x2b5a2 in JavaEventLoop () #21 0xa2214 in TtaMainLoop () #22 0x32bb1 in thotlib_APIInterface_TtaMainLoop () #23 0xca4a45 in ?? () #24 0x38a05 in do_execute_java_method (ee=0x0, obj=0xca4718, method_name=0x3657d "run", signature=0x36579 "()V", mb=0x0, isStaticCall=0) at /spare/toolkit/Thot/kaffe-0.8.4/kaffe/kaffevm/support.c:437 #25 0x365c3 in firstStartThread () at /spare/toolkit/Thot/kaffe-0.8.4/kaffe/kaffevm/thread.c:222 Not sure if you are interested on the dump given that is already known that there are synchronization problems. On a different topic, and the one I am really interested on is why Thot was not originally designed with SGML in mind? This is what one of the FreeBSD hackers had to say: jfieber@indiana.edu said: > when you get a chance, check out http://rah.star-gate.com/ > languages.html it discusses the theory of their meta language thingy. > Hm... I'm not sure what to think of this. They seem to have > expended a great deal of effort to re-invent SGML. The S language > implements most SGML concepts, but in an incompatible form with no > obvious advantage over SGML. Similarly the P and T languages look to > be an implementation of the concepts in DSSSL, although in a more > limited fashion. > So, the philosophy of Thot is more or less the same as SGML and DSSSL > almost exactly, but with an independent implementation. DSSSL is > quite new (1996), but SGML has been around over a decade so I find > this re-inventing of the Tnks! Amancio From The Desk Of Daniel Veillard : > > This is good news ! > > >I noticed that went I use back and forth Amaya sometimes seems to get > >in an idle mode and refuses to display pages from there on. > > > >Has anyone seeing this behavior? > > I guess that you use the Java version isn't it ? > The java version, when interrupted shows amount of HTML code > which is available when stopped. If empty it displays an > empty page, this should be improved. This behavious is related with > back and forth since when looking for next/previous document, if > the current one didn't finished to load, it is interrupted, hence > the white page. For some reason, sometimes, the next or previous document > is not loaded when requesting a series of next and/or back actions. > and you end-up with a white, empty page ... > This is a matter of synchronizing HTTP request initiated from > C code with the actual fetching done in the Java V.M. The DocumentLoaded > global variable can get messed up and from that point new fetchings > are not allowed. > > Only solution yet is to not go back and forth too fast :-\ > > Daniel > > -- > Daniel Veillard@w3.org | W3C / INRIA Rhone-Alpes | Today's Bookmarks : > Daniel.Veillard@inrialpes.fr| 655 av de l'Europe | Linux, WWW, Java, > Tel : +33 04 76 61 53 85 | 38330 Montbonnot | badminton, Kaffe, > Fax : +33 04 76 54 76 15 | France | Amaya and CSS. > Home: +33 04 76 63 05 86 | http://opera.inrialpes.fr/veillard > >
Received on Thursday, 15 May 1997 13:42:41 UTC