gnustep-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Sum up of current failures


From: Fred Kiefer
Subject: Re: Sum up of current failures
Date: Sat, 23 Mar 2013 14:50:44 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130307 Thunderbird/17.0.4

On 23.03.2013 09:11, Richard Frith-Macdonald wrote:

On 22 Mar 2013, at 17:03, Riccardo Mottola wrote:

Richard Frith-Macdonald wrote:
On 22 Mar 2013, at 13:24, Riccardo Mottola wrote:
How can I run a specific test, so that I can test NSCalendar and NSXMLNode ?
gnustep-tests --help

will tell you how to run tests, along with various useful options (I 
particularly like --debug ... runs gdb with breakpoints set immediately before 
failed tests)

I checked the XML tests on OpenBSD and they pass. Thus strangely they only fail 
on NetBSD.

Still, the hangs and the failures should be looked into before a release? What 
information can I give you for debugging, except ther esults which aren't very 
explicative?

It's difficult with system specific failures ... really you need to do the 
debugging on your system.

That is ..  you need to run the tests with the --debug option, and then step 
through the code in the debugger to see what's actually going wrong.

That should be enough to find most things, but of course, there's also the 
possibility that an underlying problem actually occurred before the testcase 
itsself ... in which case you need to look at the objects involved at the start 
of the test to see if they are in some unexpected state.

I think I found the root of this issue. On 2012-12-01 I made a change to NSXMLNode that used a macro for newer releases of libxml2. But I could not check that on my machine as the version of libxml2 I was using was too old. As it turns out that change was completely wrong. libxml2 uses two different buffer structures xmlBufPtr and xmlBufferPtr, only for the former that change was needed, but here we are using the later. Reverting that change solved the problem for me.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]