Page 1 of 1

qa error with 8.1.4 on Solaris

Posted: Mon Aug 23, 2004 9:23 am
by HPW
Back in the office I compiled the latest 8.1.4 on our host with SunOS 5.9 Generic.

No problem with compile.
But when I run 'qa' it throw this error:
...
...
testing-> write-line...

testing-> xml-error
testing-> Bus Error(coredump)
Then I am back at the command-prompt and there is a new dump-file.
On WIN 'qa' run fine. From the log, it seems that it crashes on 'xml-parse'.

Posted: Mon Aug 23, 2004 11:56 am
by Lutz
Its hard to say whats going on here. newLISP always passes this test on Solaris x86, so I guess that your are running on a Sparc CPU? If I could get access to a Sparc I could debug this, but without it, it is difficult.


Lutz

Posted: Mon Aug 23, 2004 12:28 pm
by HPW
>so I guess that your are running on a Sparc CPU?

Yes, our host is a 8 processor mashine.

>If I could get access to a Sparc I could debug this, but without it, it is difficult.

In the moment no problem, as long as it runs our scripts there.


PS: Luis has also a problem with xml-parse from qa on the WINCE-port.

Posted: Mon Aug 23, 2004 1:01 pm
by HPW
I have isolated the problem a bit:
Note the spave between 'value'> </hello>

On WIN:
> (xml-parse "<hello att='value'></hello>")
(("ELEMENT" "hello" (("att" "value")) ()))
> (xml-parse "<hello att='value'> </hello>")
(("ELEMENT" "hello" (("att" "value")) (("TEXT" " "))))
On SUN:
(xml-parse "<hello att='value'></hello>")
without space it crashes
(xml-parse "<hello att='value'> </hello>")
(("ELEMENT" "hello" (("att" "value")) (("TEXT" " "))))

Posted: Mon Aug 23, 2004 1:47 pm
by Lutz
Thanks, that will help to find the problem

Lutz

Posted: Mon Aug 23, 2004 3:26 pm
by Lutz
I stepped through the code with a source level debugger, trying to catch something 'fishy', but no luck so far, trying the code with and without the space.

I wonder if this alone does get the problem on the Sparc machine:

(xml-parse "<hello></hello>")

or if the attribute tag inside the 'hello' tag is necessary.

Lutz

Posted: Mon Aug 23, 2004 3:46 pm
by Lutz
I put a new nl-xml.c in http://newlisp.org/downloads/development/

this might solve the crash problem un Sun Sparc with xml-parse


Lutz

Posted: Mon Aug 23, 2004 3:46 pm
by Lutz
I put a new nl-xml.c in http://newlisp.org/downloads/development/

this might solve the crash problem un Sun Sparc with xml-parse.


Lutz

Posted: Mon Aug 23, 2004 4:14 pm
by HPW
When I am back in the office next morning, I will make the test.

Posted: Tue Aug 24, 2004 6:25 am
by HPW
Just tested it, and now it runs through without problems.

qa passed for Sparc !

Posted: Tue Aug 24, 2004 12:21 pm
by Lutz
Great news! I hope we hear the same from the PocketPC.

Lutz

Posted: Mon Sep 06, 2004 6:26 am
by HPW
The new 8.1.5 qa test gives me the following on solaris:

Code: Select all

TESTING FINISHED WITH ERRORS:                     
                                                  
>>>> net-accept failed nil                        
>>>> net-close failed nil                         
>>>> net-connect failed nil                       
>>>> net-error failed nil                         
>>>> net-listen failed nil                        
>>>> net-local failed nil                         
>>>> net-peek failed nil                          
>>>> net-peer failed nil                          
>>>> net-receive failed nil                       
>>>> net-select failed nil                        
>>>> net-send failed nil                          
>>>> net-sessions failed nil                      
process and functions using it while testing, like
pipe and some udp functions, are not tested       
test using: ./newlisp qa ext                      
read the header of this file for more info        
                                                  
true
It makes no diffenrence with/without the ext-toggle.

So

newlisp qa

and

newlisp qa ext

produce the same error!

Posted: Mon Sep 06, 2004 12:10 pm
by Lutz
My tests with 8.1.5 on both Solaris on x86 and Solaris on Sparc are running fine. Most likely something different is going on here, like not having permissions to use certain ports or something similar.

Net working routines are now tested by default and do need no enabling via the ext option.

Lutz